[sleepycal]

Thank you for the feedback. Although the README looks slightly easier than previous, it still makes for difficult reading, and I'd argue that they need to document this better. Unless you have a link to somewhere this has already been done? (a quick 5 minute look on Google didn't give any definitive answer)

[omni]

I don't have a link to any improved docs,no. I did set up a private registry at my company though and I remember it being quite painless. We just run the stock image, pass our credentials to it via environment variables, and it Just Works™. I think the README is verbose because there are a lot of options when it comes to running the thing. If you know off the bat that S3 is what you want, though, I think you can read it in a pretty targeted fashion.

[Gigablah]

Getting the private registry to work with TLS is really painful though:

https://github.com/docker/docker-registry/issues/541

[jamshid]

True, I finally broke down and just added "--insecure-registry" (it's just a cert verification issue, the connection is secure regardless). Will try again later, sounds like they're planning major registry changes anyway. Anyway, while the S3 backed private registry is kinda slow, it works and it's literally a single docker run. I'm not sure how it could be simpler. https://github.com/docker/docker-registry/blob/master/ADVANC...