Barebones but complete registry implementation for self-hosting.
Ranked in these QuestionsQuestion Ranking
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! :)
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.