5 ms·
We created contains.dev to allow quick exploring of Docker images, their contents, layers, etc. To get any sort of info about an image we found ourselves pulli
by tm11zz 5y ago
We created contains.dev to allow quick exploring of Docker images, their contents, layers, etc.
To get any sort of info about an image we found ourselves pulling them locally and spending lots of time with CLI tools and manual layer exploration.
Much like GitHub is a great way to explore different repositories quickly, we're hoping contains.dev is a step in that direction.
- jamescampbell 5y agoHow are you loading the data for all of the public repositories? It looks very similar to the front page of https://hub.docker.com/ https://hub.docker.com/. Assuming you are scraping / using the API to load all of that data?
- tm11zz 5y agoSome information is obtained from the Docker Hub API, but most of the data comes from the registries and images themselves.
- oogali 5y agoIs there a private or on-premise version for non-public registries?
- tm11zz 5y agoWe're initially focusing on private images available on one of the major registries (AWS, GCP, Azure, Docker Hub, etc.). But on-premise is definitely one of the options we want to offer in the future.