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!
GitLab Container Registry
11–20 of 121 posts
Re: GitLab Container Registry
#12Kind of unrelated, but I'm super happy to be working at GitLab. Nearly everything we do is out in the open, and most features are available in CE, which is fully open source ( https://gitlab.com/gitlab-org/gitlab-ce ). I've wanted great, open source tools that don't look like dung for a long long time, and GitLab is definitely reaching that goal. Can't help but gush about the product we're building. :D Here are some…
[deleted]
Re: GitLab Container Registry
#13Fantastic, 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.
Re: GitLab Container Registry
#14I'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 runner) which kind of leaves this "Container Registry" without value, because I still need to manually build/push my images from one machine...
Re: GitLab Container Registry
#15Awesome, a new place to host your unpatched, opaque disk images!
Re: GitLab Container Registry
#16This 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
#17am 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?
Re: GitLab Container Registry
#18This might sound like a silly question, but does this require gitlab, or can it work standalone?
Re: GitLab Container Registry
#19I'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…
Thanks, our idea is indeed to build an all-in-one solution. For more information see https://about.gitlab.com/direction/#scope
You should be able to build/push from the CI system, see the example GitLab CI configuration file in the blog post.
EDIT: For GitLab.com users using shared runners this is waiting on the Runner upgrade that we'll do in the coming days. If you use your own runner that runs 1.2 it should be fine.
Re: GitLab Container Registry
#20This might sound like a silly question, but does this require gitlab, or can it work standalone?
You install it by installing the GitLab Omnibus package. But you push and pull to it from other application too, no need to use GitLab.