4 ms·
Show HN: GitHub for Docker Images
- gvkhna 5y agoThis is great! I was working on something similar but admittedly didn’t get around to launching it, it wasn’t as nice as this. How do you plan to monetize?
- zufallsheld 5y agoAwesome tool! It'd be great if we couls use this with github1s.com (https://github1s.com/conwnet/github1s https://github1s.com/conwnet/github1s).
- fresh2dev 5y agoThis is a huge improvement over DockerHub's UI (both the UI and search), and it definitely feels like the familiar GitHub. Excellent work; bookmarked!
- tm11zz 5y agoAmazing! that's great to hear.
- derekjdanserl 5y agoThis is awesome.
- 8eye 5y agoi like this, def keep going in this direction, i am gonna check it out further tomorrow when i am more awake. great look too
- alexellisuk 5y agoThis reminds me of Microbadger that Liz Rice started with some of her friends. It's very similar. I like the integration with CVEs.. So what's the longer term vision here for contains.dev? https://github.com/microscaling/microbadger https://github.com/microscaling/microbadger
- tm11zz 5y agoGreat pointer, thanks for that. Now I'm trying to piece together what happened to that project :) The plan is to integrate with the different registries to support private images and in parallel to expand what contains.dev can do for individual images.
- deleted 5y ago[deleted]
- ubergesundheit 5y agoCool project! I would be cautious with the sentence „See what’s inside your Docker“. Aside from the broader term „container image“, I would think you could get mail from Docker (as I’m the company) for using their name while you’re not Docker.
- tm11zz 5y agoWe 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.
- cridenour 5y agoVery cool. Would be nice to have a browser extension or something to have a quick link over from hub.docker.com.
- tm11zz 5y agoThanks! that's a great idea.
- thedailypickup 5y agoLooks slick, nice job! What are the advantages of signing up?
- tm11zz 5y agoThank you! Signing up allows you to view your own private images.
- ericb 5y agoHow does it work?
- tm11zz 5y agoGenerally we process the Docker images and extract useful information and organize the data in a consumable way.