OCI Registry Explorer

oci.dag.dev

100 points·jcbhmr··7 comments

Hi, this is my project! I was surprised to see it posted here. It's a debugging tool for container images that I host for myself and some friends/coworkers.

Some of its features are intentionally not very discoverable, partially to keep the interface minimal, but mostly because I like to hide them as easter eggs.

I wrote a little more context for how this (and some related tools) came to be at https://dag.dev for the curious.

Happy to answer any questions, of course, but I imagine this is a pretty niche tool.

> Rate exceeded.

Sounds interesting, but it didn't survive the Hacker News amount of visitors.

Sorry about that. I usually don't let it scale up at all so that I don't have to worry about costs.

I've raised some limits for now so hopefully you can get through.

Wow, this is super cool! I tried this on some of my own images, and it even supports some less-common features like zstd compression and cosign signatures. It even links to the documentation for all the signature fields and to the sigstore transparency log for each signature, and it shows you the size of every individual file inside each layer too. And it's also pretty cool that the top of every page shows the shell command used to generate it.

Thanks for making it, i use it on a regular basis and it's very helpful. I could use crane but it's oftentimes quicker just to explore a registry in a browser.

oci.dag.dev is fantastic. You can also self-host it, because it's just a Golang CLI.

I compared it with various other registry browser tools, and it was clearly the best one. See here for more details: https://www.augmentedmind.de/2025/03/30/the-9-best-docker-re...

To save you a click: this is nothing to do with the Windows Registry.

Reply on news.ycombinator.com