This is really much needed (if they did it right). The container registry @ docker is terribly broken and the user experience is frustrating. I ended up using Git repositories + building on server because it was "so unusable".<p>Hopefully, this changes things.
If you want to use a reasonably priced non-Docker-run registry that is available today, check out the Google Container Registry: <a href="https://cloud.google.com/container-registry/" rel="nofollow">https://cloud.google.com/container-registry/</a><p>It recently hit GA and is super fast. You can use it from anywhere -- not just GCE.<p>(Disclaimer: I used to work at Google on GCE/GKE/Kubernetes).
This is definitely a great move for Amazon. As it is now, the docker registry is ridiculously difficult to get set up and secured.<p>That said, I find myself wishing that Amazon would contribute more back to the Docker project (specifically the registry in this case), and then provide a hosted option with IAM integration, etc.<p>The existing AWS ecosystem is already enough for me to want to stay with them, but I'd say the Docker ecosystem is fragile enough that it could use some bolstering just to keep it viable and ensure Amazon's investments don't go down the tube if something better comes along.
Can anyone comment on how this compares to <a href="http://quay.io" rel="nofollow">http://quay.io</a>? We use that, and I'm less than impressed.
Self hosting a registry (<a href="https://hub.docker.com/_/registry/" rel="nofollow">https://hub.docker.com/_/registry/</a>) on aws backed by s3 storage is fairly easy and is already available today.
What I'd really like is an all-in-one service that incorporated Docker Content Trust[0]. While I'd prefer that they'd used something a bit more mainstream (e.g. GPG), some image signing is better than none at all.<p>Doing this today requires a fair bit of extra infrastructure over a basic v2 registry, and really it'd be much nicer to have a single service that was able to manage this.<p>0: <a href="https://blog.docker.com/2015/08/content-trust-docker-1-8/" rel="nofollow">https://blog.docker.com/2015/08/content-trust-docker-1-8/</a>