When comparing Quay.io vs Docker Registry 2.0, the Slant community recommends Docker Registry 2.0 for most people. In the question“What are the best docker image private registries?” Docker Registry 2.0 is ranked 2nd while Quay.io is ranked 9th. The most important reason people chose Docker Registry 2.0 is:
Currently includes in-memory, local filesystem, Azure, and S3.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Web based UI
Quay.io has a beutiful and easy to understand web based UI.
Pro Most prominent alternative to Docker Hub
Quay was started by two Google engineers to serve as an alternative to Docker Hub. It was later acquired by CoreOS.
Pro Maintains several storage drivers to allow for different models of image retention
Currently includes in-memory, local filesystem, Azure, and S3.
Pro Simple to set up
Pro Only supports docker images
If you want more then go somewhere else! :)
Cons
Con Acquired company
CoreOS bought Quay and redirected their energies to the CoreOS Enterprise Registry, so this product might not be here for the duration.
Con Biggest CON there is that it cannot control deleting of images properly
Bottom line is this makes docker registry suck when your harddisk fills up at the wrong time and you cannot push out your builds!
Con No inbuilt access control provided
Authentication or Authorization is not provided by default and needs to be handled externally. An optional authentication should have been provided, given that docker client has inbuilt authentication.
Con Only supports docker images
Con Sometimes images disappear
Con Setting it up may require some work
Setting up the new Docker Registry 2.0 requires some more setup than usual. Especially dependencies need to be installed beforehand.