News for hackers. Stuff that matters.
Re:GitLab Container Registry by mikewhy on Monday May 23, 2016 @03:05PM (#11756038)
This is great! But I'm curious if anyone at Gitlab can comment on what this gives over running the existing docker registry? Can we configure this to use S3 to store the resulting images?

Our runner image has docker, we run our tests with docker-compose, if they pass we push them to our existing registry. In fact our .gitlab-ci.yml looks very similar to the example under "elaborate example" in the blog post.

Just wondering what we'd be missing out on if we didn't switch to Gitlab Container Registry.

Re:GitLab Container Registry by ayufan on Monday May 23, 2016 @03:15PM (#11756113)
The biggest plus of using integrated registry is that you have integrated authentication and authorization of GitLab that follow your groups and members assigned to your GitLab projects, making it really easy to have private container repositories stored on registry.

Second the built-in registry is really easy to configure and maintain. You have to specify the address and provide a certificate to start using it. You also use the same backups mechanism as you use for your GitLab installation.

In the future we may make it possible to use external storage for container images, like S3. This is something that is already supported by docker/distribution.

Re:GitLab Container Registry by fapjacks on Monday May 23, 2016 @03:57PM (#11756433)
I am super stoked to see this and will be using the crap out of it and pointing others to it (the registry is kind of a pain to get going)! It looks like this is just the v2 registry (from Distribution) integrated into Gitlab, so I'm wondering what's stopping me from backing this registry with S3? Is it just not supported by the Gitlab config yaml? I back my private registry with S3 and it's just a couple of config options to enable it. Or am I misunderstanding some fundamental concept here? Thanks for the awesome work!
Re:GitLab Container Registry by sytse on Monday May 23, 2016 @04:44PM (#11756799)
Glad to hear you're super stoked! I think you're on the money regarding the s3 backup. I think it is making the configuration accessible. I expect you can work around that by doing it yourself.
Re:GitLab Container Registry by Snappy on Monday May 23, 2016 @03:21PM (#11756155)
It really comes down to cost and convenience. We don't charge anything additional to run the container registry (including unlimited private projects for personal or business use), and it's already installed with GitLab.

Having said that, we do love deep integration, so we'll continue to improve it going forward. If you have any ideas for improvements, please do create an issue!