Re:Amazon EC2 Container Registry
by lrvick on Friday October 09, 2015 @06:03AM
(#10359092)
Speaking as someone who has paid for enterprise quay.io (CoreOS enterprise registry), and seen the source code and docker image.... Run far away. Not even the most basic security or availability precautions were taken.
A casual security evaluation revealed that all of the 20+ processes in the quay.io registry container run as real root. Worse, the system has no authentication for image uploading allowing -anyone- clobber any existing image. Auth only exists for reading images which is entirely backwards. Requests for to patch these and other holes myself were denied.
Don't even get me started on general instability or that on a failed build it would hang and never accept new ones without a manual container restart.
Had to pull the plug on the whole thing and replace it with a few git hooks and a vanilla docker registry... Which has been simple and rock solid.
A casual security evaluation revealed that all of the 20+ processes in the quay.io registry container run as real root. Worse, the system has no authentication for image uploading allowing -anyone- clobber any existing image. Auth only exists for reading images which is entirely backwards. Requests for to patch these and other holes myself were denied.
Don't even get me started on general instability or that on a failed build it would hang and never accept new ones without a manual container restart.
Had to pull the plug on the whole thing and replace it with a few git hooks and a vanilla docker registry... Which has been simple and rock solid.