Gitlab Container Registry Setup


We have a GitLab CI pipeline which builds a new Docker image based on an external ETCD snapshot of a Hashicorp Vault secrets back-end. The image is for disaster recovery so we don't have any interest in keeping old versions in the registry. Is there any way of purging GitLab registry container images which are older than a certain date.

Container orchestration solutions such as Kubernetes allow development teams to be quick and agile with their software deployments. The main feature of these orchestration tools is the ability to reduce the deployment of version piece of software down to a simple tag name on the end of a string. For example image: someApplication:canary.

  • In this case, it’s a GitLab container registry for the same private group (“my-group”), so GitLab is able to log into it automatically. Although there are still a lot of parts moving behind the scenes, this relatively small amount of configuration is all it takes to reliably connect multiple isolated components for integration testing.
  • Hi, I’m hosting a Gitlab CE run out docker for a small development firm. They’re set up with CI right now to push to dockerhub right now. Customer has asked if it is possible to use the registry functionality of GitLab itself. The setup seems straightforward, however there are a lot of blanks when you’re running behind a reverse proxy. The domain is using Cloudflare for the SSL and I.
  • GitLab Container Registry administration. With the GitLab Container Registry, every project can have its own space to store Docker images. Read more about the Docker Registry in the Docker documentation. This document is the administrator’s guide. To learn how to use the GitLab Container Registry, see the user documentation.
  • First we’ll set up the URL where the registry will reside. Then we will (optionally) configure the registry to use an S3-compatible object storage service to store its data. SSH into your GitLab server, then open up the GitLab configuration file: sudo nano /etc/gitlab/gitlab.rb Scroll down to the Container Registry settings section.

This opens the doors to streamlined deployments, but creates another problem. How do we streamline? We can do this manually, but it’s not very streamlined. Or we can do this automatically, but we need to be smart. We can’t just deploy as soon as a new version is released. We need to check it first. This is where container registries and CI/CD come in.

Gitlab Container Registry SetupGitlab

GitLab can store up to 10 GB in a container registry for projects. You can incorporate the building of these containers into your own CI/CD pipeline or you can use Gitlab’s own CI/CD functionality to do this for you. For this tutorial, you will do this by hand so you can get a grasp of the process.

In this tutorial you’ll learn how to:

  • Create a private container registry on GitLab
  • Create deployment keys
  • Create a container
  • Push to the container registry
  • Pull using your deployment key

You will only need

  • Kubernetes cluster

Find yourself a healthy Kubernetes cluster. If you don’t have access to one, install MicroK8s on your laptop at no cost. If you’re on Windows or Mac you may need to follow the Multipass guide first to get a VM with Ubuntu before you start.

Hello I started learn container, docker, etc since last week and I have a question.

Gitlab Container Registry Setup

I created a gitlab-ce container with the image available on the dockerhub :

I used a docker-compose.yaml to add the volumes and keep my modifications.

But when I go on my gitlab web interface I don’t see the “registry” section and I can’t enable it in the settings …

So what is the problem ?
Is gitlab registry only available on Gitlab-ee ? Is Gitlab registry not available in gitlab container ?

Gitlab Ce Container Registry Setup

Best regards,