Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab Container Registry

about.gitlab.com

Post reply on HN
Print view View original

21–30 of 121 posts

Re: GitLab Container Registry

#21

Post by tmaczukin »

diggan wrote: post #14

I'm excited for this, seems like GitLab is moving more into a all-in-one solution, compared to Github that focuses on "social coding", whatever that now means. So to try out this new feature (together with the pipelines), I tried setting up a simple project that uses a docker image to serve a simple html page. However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted ru…

Our shared runners should be updated within a week. Then you will be able to use Container Registry on GitLab.com without self-hosted runner.

Re: GitLab Container Registry

#22

Post by ayufan »

mikewhy wrote: post #16

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 won…

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

#24

Post by Snappy »

diggan wrote: post #14

I'm excited for this, seems like GitLab is moving more into a all-in-one solution, compared to Github that focuses on "social coding", whatever that now means. So to try out this new feature (together with the pipelines), I tried setting up a simple project that uses a docker image to serve a simple html page. However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted ru…

Yeah, sorry about that. We'll update the blog post to clarify. We're updating the CI runners this week to support this.

Re: GitLab Container Registry

#25

Post by tmaczukin »

netcraft wrote: post #17

am I correct that this is only for on-prem deployments, that they aren't going to be offering a public container registry a la docker hub or quay?

You can enable Container Registry for your projects on GitLab.com :)

And in a few days our shared runners should be updated to support the full docker workflow with the Container Registry.

Re: GitLab Container Registry

#26

Post by sytse »

FireBeyond wrote: post #13
lukebennett wrote: post #3

Fantastic, Gitlab are absolutely nailing it at the moment. Don't think there's any other hosted service offering so many CI/CD features for free under one roof. It feels like what Github did for SCM, Gitlab are doing for CI.

I agree, this is awesome. Their post yesterday hinted at something, and I honestly didn't think it would be this exciting. I can't wait to use it.

Thanks, glad you like it. BTW I wonder how many people understood our hint yesterday: "We almost can't _contain_ our excitement about how our announcement on Monday will _register_ with you!".

Re: GitLab Container Registry

#27

Post by sytse »

cridenour wrote: post #11

After GitHub moved to unlimited repositories, I started to question if our small team should stay on GitLab - and this just triple-confirmed that we will. Awesome feature for an already awesome product. Great job!

Thank you very much much. I hope your switch goes smoothly.

Re: GitLab Container Registry

#28

Post by Snappy »

ayufan wrote: post #22
mikewhy wrote: post #16

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 won…

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…

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!

Re: GitLab Container Registry

#29

Post by sytse »

davexunit wrote: post #7

Awesome, a new place to host your unpatched, opaque disk images!

I think the patching of Docker container images is a big problem. We try to provide a completely automated flow in GitLab using CI, CD, and the container registry. I would love to have a big button that says 'update all my containers'. I've made an issue https://gitlab.com/gitlab-org/gitlab-ee/issues/592

Re: GitLab Container Registry

#30

Post by lukebennett »

sytse wrote: post #26
FireBeyond wrote: post #13

Earlier quoted context omitted.

I agree, this is awesome. Their post yesterday hinted at something, and I honestly didn't think it would be this exciting. I can't wait to use it.

Thanks, glad you like it. BTW I wonder how many people understood our hint yesterday: "We almost can't _contain_ our excitement about how our announcement on Monday will _register_ with you!".

Heh, I didn't read the hint until after the registry announcement, but saw what you did and appreciated it with the benefit of hindsight!
Post reply on HN