Re:Amazon EC2 Container Registry
by datadata on Thursday October 08, 2015 @01:31PM
(#10354347)
Self hosting a registry (https://hub.docker.com/_/registry/) on aws backed by s3 storage is fairly easy and is already available today.
[ Parent
| on HN ]
I have seen a lot of people having trouble in IRC with setting it up and one more thing I have to worry about uptime myself (even if it's fairly simple) is not something I'm a fan of
Re:Amazon EC2 Container Registry
by toomuchtodo on Friday October 09, 2015 @02:34AM
(#10358493)
It's brutal and a waste of time. We're moving from our own docker registry instances to AWS' offering as soon as we get access from Amazon.
Re:Amazon EC2 Container Registry
by techdragon on Thursday October 08, 2015 @01:54PM
(#10354573)
Except that has no UI. (At least last time I checked)
Re:Amazon EC2 Container Registry
by snockerton on Thursday October 08, 2015 @02:25PM
(#10354876)
No UI out of the box (Registry:v2). DTR has a 'health' UI that is pretty worthless since you can't browse images. There are other frontend tools that work with registry:v2 though, such as Portus:
It's also, in my experience, much slower (inexplicably, since apparently Docker Hub is also backed by S3 under the hood). Using the official docker registry images (only modification was to point them to a private S3 bucket w/ credentials) resulted in frequent push/pull failures with 500 errors. Even when they succeeded, images were taking ~15-20 minutes to push. I filed a GitHub issue and the only suggestion was to decrease the chunk size, which did not improve anything.
Now we use quay.io and it's much easier and faster.