GitLab container registry administration

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed

{{< /details >}}

[!note] The next-generation container registry is now available for upgrade on GitLab Self-Managed instances. This upgraded registry supports online garbage collection, and has significant performance and reliability improvements.

With the GitLab container registry, every project can have its own space to store Docker images.

For more details about the Distribution Registry:

• Configuration
• Storage drivers
• Deploy a registry server

This document is the administrator's guide. To learn how to use the GitLab Container Registry, see the user documentation.

Enable the container registry

The process for enabling the container registry depends on the type of installation you use.

Linux package installations

If you installed GitLab by using the Linux package, the container registry may or may not be available by default.

The container registry is automatically enabled and available on your GitLab domain, port 5050 if you're using the built-in Let's Encrypt integration.

Otherwise, the container registry is not enabled. To enable it:

• You can configure it for your GitLab domain, or
• You can configure it for a different domain.

The container registry works under HTTPS by default. You can use HTTP but it's not recommended and is beyond the scope of this document.

Helm Charts installations

For Helm Charts installations, see Using the container registry. in the Helm Charts documentation.

Self-compiled installations

If you self-compiled your GitLab installation:

1. You must deploy a registry using the image corresponding to the version of GitLab you are installing (for example: registry.gitlab.com/gitlab-org/build/cng/gitlab-container-registry:v3.15.0-gitlab)
2. After the installation is complete, to enable it, you must configure the Registry's settings in gitlab.yml.
3. Use the sample NGINX configuration file from under lib/support/nginx/registry-ssl and edit it to match the host, port, and TLS certificate paths.

The contents of gitlab.yml are:

registry:
  enabled: true
  host: <registry.gitlab.example.com>
  port: <5005>
  api_url: <http://localhost:5000/>
  key: <config/registry.key>
  path: <shared/registry>
  issuer: <gitlab-issuer>

Where:

A Registry init file is not shipped with GitLab if you install it from source. Hence, restarting GitLab does not restart the Registry should you modify its settings. Read the upstream documentation on how to achieve that.

At the absolute minimum, make sure your Registry configuration has container_registry as the service and https://gitlab.example.com/jwt/auth as the realm:

auth:
  token:
    realm: <https://gitlab.example.com/jwt/auth>
    service: container_registry
    issuer: gitlab-issuer
    rootcertbundle: /root/certs/certbundle

[!warning] If auth is not set up, users can pull Docker images without authentication.

Container registry domain configuration

You can configure the Registry's external domain in either of these ways:

• Use the existing GitLab domain. The Registry listens on a port and reuses the TLS certificate from GitLab.
• Use a completely separate domain with a new TLS certificate for that domain.

Because the container registry requires a TLS certificate, cost may be a factor.

Take this into consideration before configuring the container registry for the first time.

Configure container registry under an existing GitLab domain

If the container registry is configured to use the existing GitLab domain, you can expose the container registry on a port. This way you can reuse the existing GitLab TLS certificate.

If the GitLab domain is https://gitlab.example.com and the port to the outside world is 5050, to configure the container registry:

• Edit gitlab.rb if you are using a Linux package installation.
• Edit gitlab.yml if you are using a self-compiled installation.

Ensure you choose a port different than the one that Registry listens to (5000 by default), otherwise conflicts occur.

[!note] Host and container firewall rules must be configured to allow traffic in through the port listed under the registry_external_url line, rather than the port listed under gitlab_rails['registry_port'] (default 5000).

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Your /etc/gitlab/gitlab.rb should contain the Registry URL as well as the path to the existing TLS certificate and key used by GitLab:

   rubyCopy

   registry_external_url '<https://gitlab.example.com:5050>'
   

   The registry_external_url is listening on HTTPS under the existing GitLab URL, but on a different port.

   If your TLS certificate is not in /etc/gitlab/ssl/gitlab.example.com.crt and key not in /etc/gitlab/ssl/gitlab.example.com.key uncomment the lines below:

   rubyCopy

   registry_nginx['ssl_certificate'] = "</path/to/certificate.pem>"
   registry_nginx['ssl_certificate_key'] = "</path/to/certificate.key>"
   

2. Save the file and reconfigure GitLab for the changes to take effect.

3. Validate using:

   shellCopy

   openssl s_client -showcerts -servername gitlab.example.com -connect gitlab.example.com:5050 > cacert.pem
   

If your certificate provider provides the CA Bundle certificates, append them to the TLS certificate file.

An administrator may want the container registry listening on an arbitrary port such as 5678. However, the registry and application server are behind an AWS application load balancer that only listens on ports 80 and 443. The administrator may remove the port number for registry_external_url, so HTTP or HTTPS is assumed. Then, the rules apply that map the load balancer to the registry from ports 80 or 443 to the arbitrary port. This is important if users rely on the docker login example in the container registry. Here's an example:

registry_external_url '<https://registry-gitlab.example.com>'
registry_nginx['redirect_http_to_https'] = true
registry_nginx['listen_port'] = 5678

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Open /home/git/gitlab/config/gitlab.yml, find the registry entry and configure it with the following settings:

   yamlCopy

   registry:
     enabled: true
     host: <gitlab.example.com>
     port: 5050
   

2. Save the file and restart GitLab for the changes to take effect.

3. Make the relevant changes in NGINX as well (domain, port, TLS certificates path).

{{< /tab >}}

{{< /tabs >}}

Users should now be able to sign in to the container registry with their GitLab credentials using:

docker login <gitlab.example.com:5050>

Configure container registry under its own domain

When the Registry is configured to use its own domain, you need a TLS certificate for that specific domain (for example, registry.example.com). You might need a wildcard certificate if hosted under a subdomain of your existing GitLab domain. For example, *.gitlab.example.com, is a wildcard that matches registry.gitlab.example.com, and is distinct from *.example.com.

As well as manually generated SSL certificates (explained here), certificates automatically generated by Let's Encrypt are also supported in Linux package installations.

Let's assume that you want the container registry to be accessible at https://registry.gitlab.example.com.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Place your TLS certificate and key in /etc/gitlab/ssl/<registry.gitlab.example.com>.crt and /etc/gitlab/ssl/<registry.gitlab.example.com>.key and make sure they have correct permissions:

   shellCopy

   chmod 600 /etc/gitlab/ssl/<registry.gitlab.example.com>.*
   

2. After the TLS certificate is in place, edit /etc/gitlab/gitlab.rb with:

   rubyCopy

   registry_external_url '<https://registry.gitlab.example.com>'
   

   The registry_external_url is listening on HTTPS.

3. Save the file and reconfigure GitLab for the changes to take effect.

If you have a wildcard certificate, you must specify the path to the certificate in addition to the URL, in this case /etc/gitlab/gitlab.rb looks like:

registry_nginx['ssl_certificate'] = "/etc/gitlab/ssl/certificate.pem"
registry_nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/certificate.key"

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Open /home/git/gitlab/config/gitlab.yml, find the registry entry and configure it with the following settings:

   yamlCopy

   registry:
     enabled: true
     host: <registry.gitlab.example.com>
   

2. Save the file and restart GitLab for the changes to take effect.

3. Make the relevant changes in NGINX as well (domain, port, TLS certificates path).

{{< /tab >}}

{{< /tabs >}}

Users should now be able to sign in to the container registry using their GitLab credentials:

docker login <registry.gitlab.example.com>

Configure self-signed certificates

If you want to use self-signed certificates with the container registry, you must configure the Docker daemon to trust self-signed certificates:

1. Instruct the Docker daemon to use self-signed certificates. These steps vary based on your operating system.

2. In the GitLab Runner config.toml file, mount the Docker daemon and set privileged = false:

   tomlCopy

     [runners.docker]
       image = "ruby:2.6"
       privileged = false
       volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"]
   

   Setting privileged = true takes precedence over the Docker daemon.

3. Restart Docker.

Disable container registry site-wide

When you disable the Registry by following these steps, you do not remove any existing Docker images. Docker image removal is handled by the Registry application itself.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Open /etc/gitlab/gitlab.rb and set registry['enable'] to false:

   rubyCopy

   registry['enable'] = false
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Open /home/git/gitlab/config/gitlab.yml, find the registry entry and set enabled to false:

   yamlCopy

   registry:
     enabled: false
   

2. Save the file and restart GitLab for the changes to take effect.

{{< /tab >}}

{{< /tabs >}}

Disable container registry for new projects site-wide

If the container registry is enabled, then it should be available on all new projects. To disable this function and let the owners of a project to enable the container registry by themselves, follow the steps below.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Edit /etc/gitlab/gitlab.rb and add the following line:

   rubyCopy

   gitlab_rails['gitlab_default_projects_features_container_registry'] = false
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Open /home/git/gitlab/config/gitlab.yml, find the default_projects_features entry and configure it so that container_registry is set to false:

   yamlCopy

   ## Default project features settings
   default_projects_features:
     issues: true
     merge_requests: true
     wiki: true
     snippets: false
     builds: true
     container_registry: false
   

2. Save the file and restart GitLab for the changes to take effect.

{{< /tab >}}

{{< /tabs >}}

Increase token duration

In GitLab, tokens for the container registry expire every five minutes. To increase the token duration:

1. In the upper-right corner, select Admin.
2. Select Settings > CI/CD.
3. Expand Container Registry.
4. For the Authorization token duration (minutes), update the value.
5. Select Save changes.

Container registry feature flags

Container registry feature flags are environment variable toggles that control experimental or transitional functionality in the container registry.

Unlike GitLab application feature flags, container registry feature flags:

• Are managed through registry-specific environment variables
• Are defined in the container registry codebase
• Require registry reconfiguration to change

Configure container registry feature flags

The following table lists active container registry feature flags:

To configure container registry feature flags, follow the instructions for your platform.

{{< tabs >}}

{{< tab title="Linux package" >}}

In /etc/gitlab/gitlab.rb, configure the feature flag:

registry['env'] = {
  '<REGISTRY_FF_FEATURE_NAME>' => 'true' # or 'false' to disable
}

Then, reconfigure the container registry:

sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart registry

{{< /tab >}}

{{< tab title="Helm chart (Kubernetes)" >}}

In values.yaml, configure the feature flag:

registry:
  extraEnv:
    <REGISTRY_FF_FEATURE_NAME>: "true"  # or "false" to disable

Then, upgrade values.yaml:

helm upgrade gitlab gitlab/gitlab -f values.yaml

{{< /tab >}}

{{< tab title="Docker" >}}

[!note] Setting environment variables directly in Docker Compose does not work. You must configure through gitlab.rb.

For Docker or Docker Compose, create or edit gitlab.rb:

registry['env'] = {
  '<REGISTRY_FF_FEATURE_NAME>' => 'true'
}

Mount this configuration in your Docker Compose setup and make sure GitLab reconfigures on startup.

{{< /tab >}}

{{< /tabs >}}

Configure storage for the container registry

[!warning] Do not directly modify the files or objects stored by the container registry. Anything other than the registry writing or deleting these entries can lead to instance-wide data consistency and instability issues from which recovery may not be possible.

You can configure the container registry to use various storage backends by configuring a storage driver. By default the GitLab container registry is configured to use the file system driver configuration.

For storage backends that support it, you can use object versioning to preserve, retrieve, and restore the non-current versions of every object stored in your buckets. However, this may result in higher storage usage and costs. Due to how the registry operates, image uploads are first stored in a temporary path and then transferred to a final location. For object storage backends, including S3 and GCS, this transfer is achieved with a copy followed by a delete. With object versioning enabled, these deleted temporary upload artifacts are kept as non-current versions, therefore increasing the storage bucket size. To ensure that non-current versions are deleted after a given amount of time, you should configure an object lifecycle policy with your storage provider.

The different supported drivers are:

Although most S3-compatible services should work with the container registry, we only guarantee support for AWS S3. Because we cannot assert the correctness of third-party S3 implementations, we can debug issues, but we cannot patch the registry unless an issue is reproducible against an AWS S3 bucket.

Use file system

If you want to store your images on the file system, you can change the storage path for the container registry, follow the steps below.

This path is accessible to:

• The user running the container registry daemon.
• The user running GitLab.

All GitLab, Registry, and web server users must have access to this directory.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

The default location where images are stored in Linux package installations is /var/opt/gitlab/gitlab-rails/shared/registry. To change it:

1. Edit /etc/gitlab/gitlab.rb:

   rubyCopy

   gitlab_rails['registry_path'] = "</path/to/registry/storage>"
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

The default location where images are stored in self-compiled installations is /home/git/gitlab/shared/registry. To change it:

1. Open /home/git/gitlab/config/gitlab.yml, find the registry entry and change the path setting:

   yamlCopy

   registry:
     path: shared/registry
   

2. Save the file and restart GitLab for the changes to take effect.

{{< /tab >}}

{{< /tabs >}}

Use object storage

If you want to store your container registry images in object storage instead of the local file system, you can configure one of the supported storage drivers.

For more information, see Object storage.

[!warning] GitLab does not back up Docker images that are not stored on the file system. Enable backups with your object storage provider if desired.

Configure object storage for Linux package installations

To configure object storage for your container registry:

1. Choose the storage driver you want to use.
2. Edit /etc/gitlab/gitlab.rb with the appropriate configuration.
3. Save the file and reconfigure GitLab for the changes to take effect.

{{< tabs >}}

{{< tab title="S3" >}}

The S3 storage driver integrates with Amazon S3 or any S3-compatible object storage service.

The s3_v2 driver (in Beta) uses AWS SDK v2 and only supports Signature Version 4 for authentication. This driver improves performance and reliability while ensuring compatibility with AWS authentication requirements, as support for older signature methods is deprecated. For more information, see epic 16272.

For a complete list of configuration parameters for each driver, see s3_v1 and s3_v2.

To configure the S3 storage driver, add one of the following configurations to your /etc/gitlab/gitlab.rb file:

# Deprecated: Will be removed in GitLab 19.0
registry['storage'] = {
  's3' => {
    'accesskey' => '<s3-access-key>',
    'secretkey' => '<s3-secret-key-for-access-key>',
    'bucket' => '<your-s3-bucket>',
    'region' => '<your-s3-region>',
    'regionendpoint' => '<your-s3-regionendpoint>'
  }
}

Or

# Beta: s3_v2 driver
registry['storage'] = {
  's3_v2' => {
    'accesskey' => '<s3-access-key>',
    'secretkey' => '<s3-secret-key-for-access-key>',
    'bucket' => '<your-s3-bucket>',
    'region' => '<your-s3-region>',
    'regionendpoint' => '<your-s3-regionendpoint>'
  }
}

For improved security, you can use an IAM role instead of static credentials by not including the accesskey and secretkey parameters.

To prevent storage cost increases, configure a lifecycle policy in your S3 bucket to purge incomplete multipart uploads. The container registry does not automatically clean these up. A three-day expiration policy for incomplete multipart uploads works well for most usage patterns.

[!note] loglevel settings differ between the s3_v1 and s3_v2 drivers. If you set the loglevel for the wrong driver, it is ignored and a warning message is printed.

When using some S3-compatible services with the s3_v2 driver, you may need to add the checksum_disabled parameter to disable AWS checksums:

registry['storage'] = {
  's3_v2' => {
    'accesskey' => '<s3-access-key>',
    'secretkey' => '<s3-secret-key-for-access-key>',
    'bucket' => '<your-s3-bucket>',
    'region' => '<your-s3-region>',
    'regionendpoint' => '<your-s3-regionendpoint>',
    'checksum_disabled' => true
  }
}

For S3 VPC endpoints:

registry['storage'] = {
  's3_v2' => {  # Beta driver
    'accesskey' => '<s3-access-key>',
    'secretkey' => '<s3-secret-key-for-access-key>',
    'bucket' => '<your-s3-bucket>',
    'region' => '<your-s3-region>',
    'regionendpoint' => '<your-s3-vpc-endpoint>',
    'pathstyle' => false
  }
}

S3 configuration parameters:

• <your-s3-bucket>: The name of an existing bucket. Cannot include subdirectories.
• regionendpoint: Required only when using an S3-compatible service or an AWS S3 VPC Endpoint.
• pathstyle: Controls URL formatting. Set to true for host/bucket_name/object (most S3-compatible services) or false for bucket_name.host/object (AWS S3).

To avoid 503 errors from the S3 API, add the maxrequestspersecond parameter to set a rate limit on connections:

registry['storage'] = {
  's3' => {
    'accesskey' => '<s3-access-key>',
    'secretkey' => '<s3-secret-key-for-access-key>',
    'bucket' => '<your-s3-bucket>',
    'region' => '<your-s3-region>',
    'regionendpoint' => '<your-s3-regionendpoint>',
    'maxrequestspersecond' => 100
  }
}

{{< /tab >}}

{{< tab title="Azure" >}}

The Azure storage driver integrates with Microsoft Azure Blob Storage.

[!warning] The legacy Azure storage driver was deprecated in GitLab 17.10 and is planned for removal in GitLab 19.0.

Use the azure_v2 driver (in Beta) instead. This driver offers improved performance, reliability, and modern authentication methods. While this is a breaking change, the new driver has been extensively tested to ensure a smooth transition for most configurations.

Make sure to test the new driver in non-production environments before deploying to production to identify and address any edge cases specific to your environment and usage patterns.

Report any issues or feedback using issue 525855.

For a complete list of configuration parameters for each driver, see azure_v1 and azure_v2.

To configure the Azure storage driver, add one of the following configurations to your /etc/gitlab/gitlab.rb file:

# Deprecated: Will be removed in GitLab 19.0
registry['storage'] = {
  'azure' => {
    'accountname' => '<your_storage_account_name>',
    'accountkey' => '<base64_encoded_account_key>',
    'container' => '<container_name>'
  }
}

Or

# Beta: azure_v2 driver
registry['storage'] = {
  'azure_v2' => {
    'credentials_type' => '<client_secret>',
    'tenant_id' => '<your_tenant_id>',
    'client_id' => '<your_client_id>',
    'secret' => '<your_secret>',
    'container' => '<your_container>',
    'accountname' => '<your_account_name>'
  }
}

By default, the Azure storage driver uses the core.windows.net realm. You can set another value for realm in the Azure section (for example, core.usgovcloudapi.net for Azure Government Cloud).

{{< /tab >}}

{{< tab title="GCS" >}}

The GCS storage driver integrates with Google Cloud Storage.

registry['storage'] = {
  'gcs' => {
    'bucket' => '<your_bucket_name>',
    'keyfile' => '<path/to/keyfile>',
    # If you have the bucket shared with other apps beyond the registry, uncomment the following:
    # 'rootdirectory' => '/gcs/object/name/prefix'
  }
}

GitLab supports all available parameters.

{{< /tab >}}

{{< /tabs >}}

Self-compiled installations

Configuring the storage driver is done in the registry configuration YAML file created when you deployed your Docker registry.

s3 storage driver example:

storage:
  s3:
    accesskey: '<s3-access-key>'                # Not needed if IAM role used
    secretkey: '<s3-secret-key-for-access-key>' # Not needed if IAM role used
    bucket: '<your-s3-bucket>'
    region: '<your-s3-region>'
    regionendpoint: '<your-s3-regionendpoint>'
  cache:
    blobdescriptor: inmemory
  delete:
    enabled: true

<your-s3-bucket> should be the name of a bucket that exists, and can't include subdirectories.

Migrate to object storage without downtime

[!warning] Using AWS DataSync to copy the registry data to or between S3 buckets creates invalid metadata objects in the bucket. For additional details, see Tags with an empty name. To move data to and between S3 buckets, the AWS CLI sync operation is recommended.

To migrate storage without stopping the container registry, set the container registry to read-only mode. On large instances, this may require the container registry to be in read-only mode for a while. During this time, you can pull from the container registry, but you cannot push.

1. Optional. To reduce the amount of data to be migrated, run the garbage collection tool without downtime.

2. This example uses the aws CLI. If you haven't configured the CLI before, you have to configure your credentials by running sudo aws configure. Because a non-administrator user likely can't access the container registry folder, ensure you use sudo. To check your credential configuration, run ls to list all buckets.

   shellCopy

   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 ls
   

   If you are using AWS as your back end, you do not need the --endpoint-url.

3. Copy initial data to your S3 bucket, for example with the aws CLI cp or sync command. Make sure to keep the docker folder as the top-level folder inside the bucket.

   shellCopy

   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 sync registry s3://mybucket
   

   [!note] If you have a lot of data, you may be able to improve performance by running parallel sync operations.

4. To perform the final data sync, put the container registry in read-only mode and reconfigure GitLab.

5. Sync any changes dating from after the initial data load to your S3 bucket, and delete files that exist in the destination bucket but not in the source:

   shellCopy

   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 sync registry s3://mybucket --delete --dryrun
   

   After verifying the command performs as expected, remove the --dryrun flag and run the command.

   [!warning] The --delete flag deletes files that exist in the destination but not in the source. If you swap the source and destination, all data in the Registry is deleted.

6. Verify all container registry files have been uploaded to object storage by looking at the file count returned by these two commands:

   shellCopy

   sudo find registry -type f | wc -l
   

   shellCopy

   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 ls s3://<mybucket> --recursive | wc -l
   

   The output of these commands should match, except for the content in the _uploads directories and subdirectories.

7. Configure your registry to use the S3 bucket for storage.

8. For the changes to take effect, set the Registry back to read-write mode and reconfigure GitLab.

Moving to Azure Object Storage

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

registry['storage'] = {
  'azure' => {
    'accountname' => '<your_storage_account_name>',
    'accountkey' => '<base64_encoded_account_key>',
    'container' => '<container_name>',
    'trimlegacyrootprefix' => true
  }
}

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

storage:
  azure:
    accountname: <your_storage_account_name>
    accountkey: <base64_encoded_account_key>
    container: <container_name>
    trimlegacyrootprefix: true

{{< /tab >}}

{{< /tabs >}}

By default, Azure Storage Driver uses the core.windows.net realm. You can set another value for realm in the azure section (for example, core.usgovcloudapi.net for Azure Government Cloud).

Disable redirect for storage driver

By default, users accessing a registry configured with a remote backend are redirected to the default backend for the storage driver. For example, registries can be configured using the s3 storage driver, which redirects requests to a remote S3 bucket to alleviate load on the GitLab server.

However, this behavior is undesirable for registries used by internal hosts that usually can't access public servers. To disable redirects and proxy download, set the disable flag to true as follows. This makes all traffic always go through the Registry service. This results in improved security (less surface attack as the storage backend is not publicly accessible), but worse performance (all traffic is redirected via the service).

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Edit /etc/gitlab/gitlab.rb:

   rubyCopy

   registry['storage'] = {
     's3' => {
       'accesskey' => '<s3_access_key>',
       'secretkey' => '<s3_secret_key_for_access_key>',
       'bucket' => '<your_s3_bucket>',
       'region' => '<your_s3_region>',
       'regionendpoint' => '<your_s3_regionendpoint>'
     },
     'redirect' => {
       'disable' => true
     }
   }
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Add the redirect flag to your registry configuration YAML file:

   yamlCopy

   storage:
     s3:
       accesskey: '<s3_access_key>'
       secretkey: '<s3_secret_key_for_access_key>'
       bucket: '<your_s3_bucket>'
       region: '<your_s3_region>'
       regionendpoint: '<your_s3_regionendpoint>'
     redirect:
       disable: true
     cache:
       blobdescriptor: inmemory
     delete:
       enabled: true
   

2. Save the file and restart GitLab for the changes to take effect.

{{< /tab >}}

{{< /tabs >}}

Encrypted S3 buckets

You can use server-side encryption with AWS KMS for S3 buckets that have SSE-S3 or SSE-KMS encryption enabled by default. Customer master keys (CMKs) and SSE-C encryption aren't supported because this requires sending the encryption keys in every request.

For SSE-S3, you must enable the encrypt option in the registry settings. How you do this depends on how you installed GitLab. Follow the instructions here that match your installation method.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Edit /etc/gitlab/gitlab.rb:

   rubyCopy

   registry['storage'] = {
     's3' => {
       'accesskey' => '<s3_access_key>',
       'secretkey' => '<s3_secret_key_for_access_key>',
       'bucket' => '<your_s3_bucket>',
       'region' => '<your_s3_region>',
       'regionendpoint' => '<your_s3_regionendpoint>',
       'encrypt' => true
     }
   }
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Edit your registry configuration YAML file:

   yamlCopy

   storage:
     s3:
       accesskey: '<s3_access_key>'
       secretkey: '<s3_secret_key_for_access_key>'
       bucket: '<your_s3_bucket>'
       region: '<your_s3_region>'
       regionendpoint: '<your_s3_regionendpoint>'
       encrypt: true
   

2. Save the file and restart GitLab for the changes to take effect.

{{< /tab >}}

{{< /tabs >}}

Storage limitations

There is no storage limitation, which means a user can upload an infinite amount of Docker images with arbitrary sizes. This setting should be configurable in future releases.

Change the registry's internal port

The Registry server listens on localhost at port 5000 by default, which is the address for which the Registry server should accept connections. In the examples below we set the Registry's port to 5010.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

1. Open /etc/gitlab/gitlab.rb and set registry['registry_http_addr']:

   rubyCopy

   registry['registry_http_addr'] = "localhost:5010"
   

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

1. Open the configuration file of your Registry server and edit the http:addr value:

   yamlCopy

   http:
     addr: localhost:5010
   

2. Save the file and restart the Registry server.

{{< /tab >}}

{{< /tabs >}}

Disable container registry per project

If Registry is enabled in your GitLab instance, but you don't need it for your project, you can disable it from your project's settings.

Use an external container registry with GitLab as an auth endpoint

[!warning] Using third-party container registries in GitLab was deprecated in GitLab 15.8 and support ended in GitLab 16.0. If you need to use third-party container registries instead of the GitLab container registry, tell us about your use cases in feedback issue 958.

If you use an external container registry, some features associated with the container registry may be unavailable or have inherent risks.

For the integration to work, the external registry must be configured to use a JSON Web Token to authenticate with GitLab. The external registry's runtime configuration must have the following entries:

auth:
  token:
    realm: https://<gitlab.example.com>/jwt/auth
    service: container_registry
    issuer: gitlab-issuer
    rootcertbundle: /root/certs/certbundle

Without these entries, the registry logins cannot authenticate with GitLab. GitLab also remains unaware of nested image names under the project hierarchy, like registry.example.com/group/project/image-name:tag or registry.example.com/group/project/my/image-name:tag, and only recognizes registry.example.com/group/project:tag.

Linux package installations

You can use GitLab as an auth endpoint with an external container registry.

1. Open /etc/gitlab/gitlab.rb and set necessary configurations:

   rubyCopy

   gitlab_rails['registry_enabled'] = true
   gitlab_rails['registry_api_url'] = "https://<external_registry_host>:5000"
   gitlab_rails['registry_issuer'] = "gitlab-issuer"
   

   • gitlab_rails['registry_enabled'] = true is needed to enable GitLab container registry features and authentication endpoint. The GitLab bundled container registry service does not start, even with this enabled.
   • gitlab_rails['registry_api_url'] = "http://<external_registry_host>:5000" must be changed to match the host where Registry is installed. It must also specify https if the external registry is configured to use TLS.

2. A certificate-key pair is required for GitLab and the external container registry to communicate securely. You need to create a certificate-key pair, configuring the external container registry with the public certificate (rootcertbundle) and configuring GitLab with the private key. To do that, add the following to /etc/gitlab/gitlab.rb:

   rubyCopy

   # registry['internal_key'] should contain the contents of the custom key
   # file. Line breaks in the key file should be marked using `\n` character
   # Example:
   registry['internal_key'] = "---BEGIN RSA PRIVATE KEY---\nMIIEpQIBAA\n"
   
   # Optionally define a custom file for a Linux package installation to write the contents
   # of registry['internal_key'] to.
   gitlab_rails['registry_key_path'] = "/custom/path/to/registry-key.key"
   

   Each time reconfigure is executed, the file specified at registry_key_path gets populated with the content specified by internal_key. If no file is specified, Linux package installations default it to /var/opt/gitlab/gitlab-rails/etc/gitlab-registry.key and populates it.

3. To change the container registry URL displayed in the GitLab Container Registry pages, set the following configurations:

   rubyCopy

   gitlab_rails['registry_host'] = "<registry.gitlab.example.com>"
   gitlab_rails['registry_port'] = "5005"
   

4. Save the file and reconfigure GitLab for the changes to take effect.

Self-compiled installations

1. Open /home/git/gitlab/config/gitlab.yml, and edit the configuration settings under registry:

   yamlCopy

   ## Container registry
   
   registry:
     enabled: true
     host: "<registry.gitlab.example.com>"
     port: "5005"
     api_url: "https://<external_registry_host>:5000"
     path: /var/lib/registry
     key: </path/to/keyfile>
     issuer: gitlab-issuer
   

   Read more about what these parameters mean.

2. Save the file and restart GitLab for the changes to take effect.

Configure container registry notifications

{{< history >}}

• threshold deprecated in GitLab 17.0, but still usable to ensure backwards compatibility.

{{< /history >}}

You can configure the container registry to send webhook notifications in response to events happening in the registry.

Read more about the container registry notifications configuration options in the Docker Registry notifications documentation.

[!warning] The threshold parameter was deprecated in GitLab 17.0, but is still usable to ensure backwards compatibility. This parameter could be scheduled for removal in a future milestone. Use maxretries instead. The registry automatically translates existing threshold configurations to equivalent maxretries values based on your configured backoff duration, and emits a deprecation warning in logs showing the translated value. While your existing configuration continues to work, you should set maxretries to avoid automatic translation.

You can configure multiple endpoints for the container registry.

{{< tabs >}}

{{< tab title="Linux package (Omnibus)" >}}

To configure a notification endpoint for a Linux package installation:

1. Edit /etc/gitlab/gitlab.rb:

   rubyCopy

   registry['notifications'] = [
     {
       'name' => '<test_endpoint>',
       'url' => 'https://<gitlab.example.com>/api/v4/container_registry_event/events',
       'timeout' => '500ms',
       'threshold' => 5, # DEPRECATED: use `maxretries` instead.
       'maxretries' => 5,
       'backoff' => '1s',
       'headers' => {
         "Authorization" => ["<AUTHORIZATION_EXAMPLE_TOKEN>"]
       }
     }
   ]
   
   gitlab_rails['registry_notification_secret'] = '<AUTHORIZATION_EXAMPLE_TOKEN>' # Must match the auth token in registry['notifications']
   

   [!note] Replace <AUTHORIZATION_EXAMPLE_TOKEN> with a case-sensitive alphanumeric string that starts with a letter. You can generate one with < /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c 32 | sed "s/^[0-9]*//"; echo

2. Save the file and reconfigure GitLab for the changes to take effect.

{{< /tab >}}

{{< tab title="Self-compiled (source)" >}}

Configuring the notification endpoint is done in your registry configuration YAML file created when you deployed your Docker registry.

Example:

notifications:
  endpoints:
    - name: <alistener>
      disabled: false
      url: https://<my.listener.com>/event
      headers: <http.Header>
      timeout: 500
      threshold: 5 # DEPRECATED: use `maxretries` instead.
      maxretries: 5
      backoff: 1000

{{< /tab >}}

{{< /tabs >}}

Run the cleanup policy

Prerequisites:

• If you use a distributed architecture where the container registry runs on a different node than Sidekiq, follow the steps in Configure the container registry when using an external Sidekiq.

After you create a cleanup policy, you can run it immediately to reduce the container registry storage space. You don't have to wait for the scheduled cleanup.

To reduce the amount of container registry disk space used by a given project, administrators can:

1. Check disk space usage by project to identify projects that need cleanup.
2. Run the cleanup policy using the GitLab Rails console to remove image tags.
3. Run garbage collection to remove unreferenced layers and untagged manifests.

Registry Disk Space Usage by Project

To find the disk space used by each project, run the following in the GitLab Rails console:

projects_and_size = [["project_id", "creator_id", "registry_size_bytes", "project path"]]
# You need to specify the projects that you want to look through. You can get these in any manner.
projects = Project.last(100)

registry_metadata_database = ContainerRegistry::GitlabApiClient.supports_gitlab_api?

if registry_metadata_database
  projects.each do |project|
    size = project.container_repositories_size
    if size > 0
      projects_and_size << [project.project_id, project.creator&.id, size, project.full_path]
    end
  end
else
  projects.each do |project|
    project_layers = {}

    project.container_repositories.each do |repository|
      repository.tags.each do |tag|
        tag.layers.each do |layer|
          project_layers[layer.digest] ||= layer.size
        end
      end
    end

    total_size = project_layers.values.compact.sum
    if total_size > 0
      projects_and_size << [project.project_id, project.creator&.id, total_size, project.full_path]
    end
  end
end

# print it as comma separated output
projects_and_size.each do |ps|
   puts "%s,%s,%s,%s" % ps
end

[!note] The script calculates size based on container image layers. Because layers can be shared across multiple projects, the results are approximate but give a good indication of relative disk usage between projects.

To remove image tags by running the cleanup policy, run the following commands in the GitLab Rails console:

# Numeric ID of the project whose container registry should be cleaned up
P = <project_id>

# Numeric ID of a user with Developer, Maintainer, or Owner role for the project
U = <user_id>

# Get required details / objects
user    = User.find_by_id(U)
project = Project.find_by_id(P)
policy  = ContainerExpirationPolicy.find_by(project_id: P)

# Loop through each container repository
project.container_repositories.find_each do |repo|
  puts repo.attributes

  # Start the tag cleanup
  puts Projects::ContainerRepository::CleanupTagsService.new(container_repository: repo, current_user: user, params: policy.attributes.except("created_at", "updated_at")).execute
end

You can also run cleanup on a schedule.

To enable cleanup policies for all projects instance-wide, you need to find all projects with a container registry, but with the cleanup policy disabled:

# Find all projects where Container registry is enabled, and cleanup policies disabled

projects = Project.find_by_sql ("SELECT * FROM projects WHERE id IN (SELECT project_id FROM container_expiration_policies WHERE enabled=false AND id IN (SELECT project_id FROM container_repositories))")

# Loop through each project
projects.each do |p|

# Print project IDs and project full names
    puts "#{p.id},#{p.full_name}"
end

Container registry metadata database

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed

{{< /details >}}

{{< history >}}

• Generally available in GitLab 17.3.

{{< /history >}}

The metadata database enables many new registry features, including online garbage collection, and increases the efficiency of many registry operations. See the Container registry metadata database page for details.

Container registry garbage collection

Prerequisites:

• You must have installed GitLab by using a Linux package or the GitLab Helm chart.

[!note] Retention policies in an object storage provider, such as Amazon S3 Lifecycle, may prevent objects from being properly deleted.

The container registry can use considerable amounts of storage space, and you might want to reduce storage usage. Among the listed options, deleting tags is the most effective option. However, tag deletion alone does not delete image layers, it only leaves the underlying image manifests untagged.

To more effectively free up space, the container registry has a garbage collector that can delete unreferenced layers and (optionally) untagged manifests.

To start the garbage collector, run the following gitlab-ctl command:

sudo gitlab-ctl registry-garbage-collect

The time required to perform garbage collection is proportional to the container registry data size.

[!warning] The registry-garbage-collect command shuts down the container registry prior to the garbage collection and only starts it again after garbage collection completes. If you prefer to avoid downtime, you can manually set the container registry to read-only mode and bypass gitlab-ctl.

This command proceeds only if legacy metadata is in use. This command does not proceed if the container registry metadata database is enabled.

Understanding the content-addressable layers

Consider the following example, where you first build the image:

# This builds a image with content of sha256:<111111...>
docker build -t <my.registry.com>/<my.group>/<my.project>:latest .
docker push <my.registry.com>/<my.group>/<my.project>:latest

Now, you do overwrite latest with a new version:

# This builds a image with content of sha256:<222222...>
docker build -t <my.registry.com>/<my.group>/<my.project>:latest .
docker push <my.registry.com>/<my.group>/<my.project>:latest

Now, the latest tag points to manifest of sha256:<222222...>. Due to the architecture of registry, this data is still accessible when pulling the image <my.registry.com>/<my.group>/<my.project>@sha256:<111111...>, though it is no longer directly accessible via the latest tag.

Remove unreferenced layers

Image layers are the bulk of the container registry storage. A layer is considered unreferenced when no image manifest references it. Unreferenced layers are the default target of the container registry garbage collector.

If you did not change the default location of the configuration file, run:

sudo gitlab-ctl registry-garbage-collect

If you changed the location of the container registry config.yml:

sudo gitlab-ctl registry-garbage-collect /path/to/config.yml

You can also remove all untagged manifests and unreferenced layers to recover additional space.

Removing untagged manifests and unreferenced layers

By default the container registry garbage collector ignores images that are untagged, and users can keep pulling untagged images by digest. Users can also re-tag images in the future, making them visible again in the GitLab UI and API.

If you do not care about untagged images and the layers exclusively referenced by these images, you can delete them all. Use the -m flag on the registry-garbage-collect command:

sudo gitlab-ctl registry-garbage-collect -m

If you are unsure about deleting untagged images, back up your registry data before proceeding.

Performing garbage collection without downtime

To do garbage collection while keeping the container registry online, put the registry in read-only mode and bypass the built-in gitlab-ctl registry-garbage-collect command.

You can pull but not push images while the container registry is in read-only mode. The container registry must remain in read-only for the full duration of the garbage collection.

By default, the registry storage path is /var/opt/gitlab/gitlab-rails/shared/registry.

To enable the read-only mode:

1. In /etc/gitlab/gitlab.rb, specify the read-only mode:

   rubyCopy

   registry['storage'] = {
     'filesystem' => {
       'rootdirectory' => "<your_registry_storage_path>"
     },
     'maintenance' => {
       'readonly' => {
         'enabled' => true
       }
     }
   }
   

2. Save and reconfigure GitLab:

   shellCopy

   sudo gitlab-ctl reconfigure
   

   This command sets the container registry into the read-only mode.

3. Next, trigger one of the garbage collect commands:

   shellCopy

   # Remove unreferenced layers
   sudo /opt/gitlab/embedded/bin/registry garbage-collect /var/opt/gitlab/registry/config.yml
   
   # Remove untagged manifests and unreferenced layers
   sudo /opt/gitlab/embedded/bin/registry garbage-collect -m /var/opt/gitlab/registry/config.yml
   

   This command starts the garbage collection. The time to complete is proportional to the registry data size.

4. Once done, in /etc/gitlab/gitlab.rb change it back to read-write mode:

   rubyCopy

   registry['storage'] = {
     'filesystem' => {
       'rootdirectory' => "<your_registry_storage_path>"
     },
     'maintenance' => {
       'readonly' => {
         'enabled' => false
       }
     }
   }
   

5. Save and reconfigure GitLab:

   shellCopy

   sudo gitlab-ctl reconfigure
   

Running the garbage collection on schedule

Ideally, you want to run the garbage collection of the registry regularly on a weekly basis at a time when the registry is not being in-use. The simplest way is to add a new crontab job that it runs periodically once a week.

Create a file under /etc/cron.d/registry-garbage-collect:

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# Run every Sunday at 04:05am
5 4 * * 0  root gitlab-ctl registry-garbage-collect

You may want to add the -m flag to remove untagged manifests and unreferenced layers.

Stop garbage collection

If you anticipate stopping garbage collection, you should manually run garbage collection as described in Performing garbage collection without downtime. You can then stop garbage collection by pressing <kbd>Control</kbd>+<kbd>C</kbd>.

Otherwise, interrupting gitlab-ctl could leave your registry service in a down state. In this case, you must find the garbage collection process itself on the system so that the gitlab-ctl command can bring the registry service back up again.

Also, there's no way to save progress or results during the mark phase of the process. Only once blobs start being deleted is anything permanent done.

Continuous zero-downtime garbage collection

You can run garbage collection in the background without the need to schedule it or require read-only mode, if you migrate to the metadata database.

Scaling by component

This section outlines the potential performance bottlenecks as registry traffic increases by component. Each subsection is roughly ordered by recommendations that benefit from smaller to larger registry workloads. The registry is not included in the reference architectures, and there are no scaling guides which target number of seats or requests per second.

Database

1. Move to a separate database: As database load increases, scale vertically by moving the registry metadata database to a separate physical database. A separate database can increase the amount of resources available to the registry database while isolating the traffic produced by the registry.
2. Move to a HA PostgreSQL third-party solution: Similar to Praefect, moving to a reputable provider or solution enables HA and is suitable for multi-node registry deployments. You must pick a provider that supports native Postgres partitioning, triggers, and functions, as the registry makes heavy use of these.

Registry server

1. Move to a separate node: A separate node is one way to scale vertically to increase the resources available to the container registry server process.
2. Run multiple registry nodes behind a load balancer: While the registry can handle a high amount of traffic with a single large node, the registry is generally intended to scale horizontally with multiple deployments. Configuring multiple smaller nodes also enables techniques such as autoscaling.

Redis Cache

Enabling the Redis cache improves performance, but also enables features such as renaming repositories.

1. Redis Server: A single Redis instance is supported and is the simplest way to access the benefits of the Redis caching.
2. Redis Sentinel: Redis Sentinel is also supported and enables the cache to be HA.
3. Redis Cluster: Redis Cluster can also be used for further scaling as deployments grow.

Storage

1. Local file system: A local file system is the default and is relatively performant, but not suitable for multi-node deployments or a large amount of registry data.
2. Object storage: Use object storage to enable the practical storage of a larger amount of registry data. Object storage is also suitable for multi-node registry deployments.

Online garbage collection

1. Adjust defaults: If online garbage collection is not reliably clearing the review queues, you can adjust the interval settings in the manifests and blobs sections under the gc configuration section. The default is 5s, and these can be configured with milliseconds as well, for example 500ms.
2. Scale horizontally with the registry server: If you are scaling the registry application horizontally with multi-node deployments, online garbage collection automatically scales without the need for configuration changes.

Configure GitLab and registry on separate nodes (Linux package installations)

By default, the GitLab package assumes both services run on the same node. Running them on separate nodes requires separate configuration.

Configuration options

The following configuration options should be set in /etc/gitlab/gitlab.rb on the respective nodes.

Registry node settings

[!warning] Support for authenticating requests using Amazon S3 Signature Version 2 in the container registry is deprecated in GitLab 17.8 and is planned for removal in 19.0. Use Signature Version 4 instead. This is a breaking change. For more information, see issue 1449.

GitLab node settings

Set up the nodes

To configure GitLab and the container registry on separate nodes:

1. On the registry node, edit /etc/gitlab/gitlab.rb with the following settings:

   rubyCopy

   # Registry server details
   # - IP address: 10.30.227.194
   # - Domain: registry.example.com
   
   # Disable unneeded services
   gitlab_workhorse['enable'] = false
   puma['enable'] = false
   sidekiq['enable'] = false
   postgresql['enable'] = false
   redis['enable'] = false
   gitlab_kas['enable'] = false
   gitaly['enable'] = false
   nginx['enable'] = false
   
   # Configure registry settings
   registry['enable'] = true
   registry['registry_http_addr'] = '0.0.0.0:5000'
   registry['token_realm'] = 'https://<gitlab.example.com>'
   registry['http_secret'] = '<6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b>'
   
   # Configure GitLab Rails settings
   gitlab_rails['registry_issuer'] = 'omnibus-gitlab-issuer'
   gitlab_rails['registry_key_path'] = '/etc/gitlab/gitlab-registry.key'
   

2. On the GitLab node, edit /etc/gitlab/gitlab.rb with the following settings:

   rubyCopy

   # GitLab server details
   # - IP address: 10.30.227.149
   # - Domain: gitlab.example.com
   
   # Configure GitLab URL
   external_url 'https://<gitlab.example.com>'
   
   # Configure registry settings
   gitlab_rails['registry_enabled'] = true
   gitlab_rails['registry_api_url'] = '<http://10.30.227.194:5000>'
   gitlab_rails['registry_host'] = '<registry.example.com>'
   gitlab_rails['registry_port'] = 5000
   gitlab_rails['registry_issuer'] = 'omnibus-gitlab-issuer'
   gitlab_rails['registry_key_path'] = '/etc/gitlab/gitlab-registry.key'
   

3. Synchronize the /etc/gitlab/gitlab-secrets.json file between both nodes:

   1. Copy the file from the GitLab node to the registry node.
   2. Ensure file permissions are correct.
   3. Run sudo gitlab-ctl reconfigure on both nodes.

Container registry architecture

Users can store their own Docker images in the container registry. Because the registry is client facing, the registry is directly exposed on the web server or load balancer (LB).

%%{init: { "fontFamily": "GitLab Sans" }}%%
flowchart LR
    accTitle: Container registry authentication flow
    accDescr: Shows how users authenticate with the container registry with GitLab API to push and pull Docker images

    A[User] --->|1: Docker loginon port 443| C{Frontend loadbalancer}
    C --->|2: connection attemptwithout token fails| D[Container registry]
    C --->|5: connect with token succeeds| D[Container registry]
    C --->|3: Dockerrequests token| E[API frontend]
    E --->|4:API returnssigned token| C

    linkStyle 1 stroke-width:4px,stroke:red
    linkStyle 2 stroke-width:4px,stroke:green

The authentication flow includes these steps:

1. A user runs docker login registry.gitlab.example on their client. This request reaches the web server (or LB) on port 443.
2. The web server connects to the registry backend pool (port 5000 by default). Because the user does not have a valid token, the registry returns a 401 Unauthorized HTTP code and a URL to get a token. The URL is defined by the token_realm setting in the registry configuration and points to the GitLab API.
3. The Docker client connects to the GitLab API and obtains a token.
4. The API signs the token with the registry key and sends it to the Docker client.
5. The Docker client logs in again with the token received from the API. The authenticated client can now push and pull Docker images.

Reference: https://distribution.github.io/distribution/spec/auth/token/

Communication between GitLab and the container registry

The container registry cannot authenticate users internally, so it validates credentials through GitLab. The connection between the registry and GitLab is TLS encrypted.

GitLab uses the private key to sign tokens, and the registry uses the public key provided by the certificate to validate the signature.

By default, a self-signed certificate key pair is generated for all installations. You can override this behavior using the internal_key setting in the registry configuration.

The following steps describe the communication flow:

1. GitLab interacts with the registry using the registry's private key. When a registry request is sent, a short-lived (10 minutes), namespace-limited token is generated and signed with the private key.
2. The registry verifies that the signature matches the registry certificate specified in its configuration and allows the operation.
3. GitLab processes background jobs through Sidekiq, which also interacts with the registry. These jobs communicate directly with the registry to handle image deletion.

Migrate from a third-party registry

Using external container registries in GitLab was deprecated in GitLab 15.8 and the end of support occurred in GitLab 16.0. See the deprecation notice for more details.

The integration is not disabled in GitLab 16.0, but support for debugging and fixing issues is no longer provided. Additionally, the integration is no longer being developed or enhanced with new features. Third-party registry functionality might be completely removed after the new GitLab container registry version is available for GitLab Self-Managed (see epic 5521). Only the GitLab container registry is planned to be supported.

This section has guidance for administrators migrating from third-party registries to the GitLab container registry. If the third-party container registry you are using is not listed here, you can describe your use cases in the feedback issue.

For all of the instructions provided below, you should try them first on a test environment. Make sure everything continues to work as expected before replicating it in production.

Docker Distribution Registry

The Docker Distribution Registry was donated to the CNCF and is now known as the Distribution Registry. This registry is the open source implementation that the GitLab container registry is based on. The GitLab container registry is compatible with the basic functionality provided by the Distribution Registry, including all the supported storage backends. To migrate to the GitLab container registry you can follow the instructions on this page, and use the same storage backend as the Distribution Registry. The GitLab container registry should accept the same configuration that you are using for the Distribution Registry.

Max retries for deleting container images

{{< history >}}

• Introduced in GitLab 17.5 with a flag named set_delete_failed_container_repository. Disabled by default.
• Generally available in GitLab 17.6. Feature flag set_delete_failed_container_repository removed.

{{< /history >}}

Errors could happen when deleting container images, so deletions are retried to ensure the error is not a transient issue. Deletion is retried up to 10 times, with a back off delay between retries. This delay gives more time between retries for any transient errors to resolve.

Setting a maximum number of retries also helps detect if there are any persistent errors that haven't been solved in between retries. After a deletion fails the maximum number of retries, the container repository status is set to delete_failed. With this status, the repository no longer retries deletions.

You should investigate any container repositories with a delete_failed status and try to resolve the issue. After the issue is resolved, you can set the repository status back to delete_scheduled so images can start to be deleted again. To update the repository status, from the rails console:

container_repository = ContainerRepository.find(<id>)
container_repository.update(status: 'delete_scheduled')