We just released Gandalf.io, a private docker registry-as-a-service. We've kept it really simple and affordable. The first private docker is free and the rest come in plans all priced at $1 / docker.
We built Gandalf.io as an internal tool to manage and access our dockers and liked it so much we're releasing it as a service.<p>Gandalf.io is built by a small team of developers for fellow developers. We're eager to do more like managing trusted builds, continuous integration and continuous deployment, as a single pipeline using only dockers on our platform. For now though we think empowering teams to get started with dockers by sharing them easily and using the standard docker cli will do.
I'm a Docker newbie but, don't private registries go against the spirit of Docker and basically every infrastructure automation tool created in last 5 years? I can't even see enterprisey companies finding this useful because their IT policies are so strict that having config on someone else's servers, private or not, is against their wonky rules.
I'm uncertain as to why I'd use this over the official project offering [ <a href="https://index.docker.io/plans/" rel="nofollow">https://index.docker.io/plans/</a> ] at roughly the same price point? [e.g. $50/month = 50]?
There are already private Docker registries out there. My company uses <a href="https://quay.io" rel="nofollow">https://quay.io</a> , for example, and Docker has its own private registry. How does Gandalf compare to these existing offerings, besides on price?<p>Security for Docker images is just as important, and in some cases more important than it is for code assets. What protection does Gandalf offer against unauthorized downloading of images/layers, and tampering with images stored in the repository?<p>Does Gandalf plan to support features like building images from a Dockerfile, ideally sent via GitHub repo hook? This is a great workflow convenience offered by both Quay and Docker.
Constructive criticism =/= trolling.<p>Please don't equate the two when posting on HN. People here are offering comments, insight, and opinions. It shouldn't be surprising if they are not in agreement with you on certain aspects.<p>That being said, best of luck!
Maybe I grok access privs incorrectly but..<p>Personal user data
Full access
This application will be able to read and write all user data. This includes the following:<p>Private email addresses
Profile information
Followers<p>Why read AND write? Why all data?
So what are sizing limits on each "repo" you offer? Unlimited?<p>I could not find a FAQ-esq section on your page, and was too lazy to "sign up to (possibly) find out".