3 ms·

Self hosting a registry (https://hub.docker.com/_/registry/ https://hub.docker.com/_/registry/) on aws backed by s3 storage is fairly easy and is already availa

• techdragon 11y ago
  Except that has no UI. (At least last time I checked)
  • snockerton 11y ago
    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: https://github.com/SUSE/Portus https://github.com/SUSE/Portus
  • vidarh 11y ago
    What would you actually want to use the UI for? For my part, all interactions with the registry are entirely automated. We set it up, and I forgot all about it. It's low level plumbing.
  • bkeroack 11y ago
    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.
• shlant 11y ago
  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
  • toomuchtodo 11y ago
    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.