docker-gitlab Documentation

Container Registry Copy Section

GitLab Container Registry

Since 8.8.0 GitLab introduces a container registry. GitLab is helping to authenticate the user against the registry and proxy it via Nginx. By Registry we mean the registry from docker whereas Container Registry is the feature in GitLab.

• GitLab Container Registry
  • Prerequisites
  • Installation
    • Setup with Nginx as Reverse Proxy
      • Create auth tokens
      • Update docker-compose.yml
      • Nginx Site Configuration
  • Configuration
    • Available Parameters
    • Container Registry storage driver
      • Example for Amazon Simple Storage Service (s3)
    • Storage limitations
  • Maintenance
    • Creating Backups
    • Restoring Backups
  • Upgrading from an existing GitLab installation

Prerequisites Copy Chapter

• Docker Distribution >= 2.4
• Docker GitLab >= 8.8.5-1

Installation Copy Chapter

Setup with Nginx as Reverse Proxy Copy Section

We assume that you already have Nginx installed on your host system and that
you use a reverse proxy configuration to connect to your GitLab container.

In this example we use a dedicated domain for the registry. The URLs for
the GitLab installation and the registry are:

• git.example.com
• registry.example.com

Note: You could also run everything on the same domain and use different ports
instead. The required configuration changes below should be straightforward.

Create auth tokens

GitLab needs a certificate ("auth token") to talk to the registry API. The
tokens must be provided in the /certs directory of your container. You could
use an existing domain certificate or create your own with a very long
lifetime like this:

mkdir certs
cd certs
# Generate a random password password_file used in the next commands
openssl rand -hex -out password_file 32
# Create a PKCS#10 certificate request
openssl req -new -passout file:password_file -newkey rsa:4096 -batch > registry.csr
# Convert RSA key
openssl rsa -passin file:password_file -in privkey.pem -out registry.key
# Generate certificate
openssl x509 -in registry.csr -out registry.crt -req -signkey registry.key -days 10000

It doesn't matter which details (domain name, etc.) you enter during key
creation. This information is not used at all.

Update docker-compose.yml

[!important]
Docker Registry v3 is currently not compatible with the JWT tokens signed by GitLab.
The example below uses registry:2 to avoid issues in validating the token.

Alternatively, you can generate a JWKS file and specify it as REGISTRY_AUTH_TOKEN_JWKS
to run registry:latest. Further information can be found here.

First add the configuration for the registry container to your docker-compose.yml.

registry:
        image: registry:2
        restart: always
        expose:
            - "5000"
        ports:
            - "5000:5000"
        volumes:
            - ./gitlab/shared/registry:/registry
            - ./certs:/certs
        environment:
            - REGISTRY_LOG_LEVEL=info
            - REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registry
            - REGISTRY_AUTH_TOKEN_REALM=https://git.example.com/jwt/auth
            - REGISTRY_AUTH_TOKEN_SERVICE=container_registry
            - REGISTRY_AUTH_TOKEN_ISSUER=gitlab-issuer
            - REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE=/certs/registry.crt
            - REGISTRY_STORAGE_DELETE_ENABLED=true

Important:

1. Don't change REGISTRY_AUTH_TOKEN_SERVICE. It must have
   container_registry as value.
2. REGISTRY_AUTH_TOKEN_REALM must look like
   https://git.example.com/jwt/auth. So the endpoint must be /jwt/auth.

These configuration options are required by the GitLab Container Registry.

Then update the volumes and environment sections of your gitlab container:

gitlab:
        environment:
            # ...
            # Registry
            - GITLAB_REGISTRY_ENABLED=true
            - GITLAB_REGISTRY_HOST=registry.example.com
            - GITLAB_REGISTRY_PORT=443
            - GITLAB_REGISTRY_API_URL=http://registry:5000
            - GITLAB_REGISTRY_KEY_PATH=/certs/registry.key

        volumes:
            - ./gitlab:/home/git/data
            - ./certs:/certs

Nginx Site Configuration

/* Detailed source-code truncated for AI context efficiency. */

Configuration Copy Chapter

Available Parameters Copy Section

Here is an example of all configuration parameters that can be used in the GitLab container.

...
gitlab:
    ...
    environment:
    - GITLAB_REGISTRY_ENABLED=true
    - GITLAB_REGISTRY_HOST=registry.gitlab.example.com
    - GITLAB_REGISTRY_API_URL=http://registry:5000
    - GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key
    - GITLAB_REGISTRY_ISSUER=gitlab-issuer
    - SSL_REGISTRY_KEY_PATH=/certs/registry.key
    - SSL_REGISTRY_CERT_PATH=/certs/registry.crt

where:

For more info look at Available Configuration Parameters.

A minimum set of these parameters are required to use the GitLab Container Registry feature.

...
gitlab:
    environment:
    - GITLAB_REGISTRY_ENABLED=true
    - GITLAB_REGISTRY_HOST=registry.gitlab.example.com
    - GITLAB_REGISTRY_API_URL=http://registry:5000
    - GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key
    - GITLAB_REGISTRY_ISSUER=gitlab-issuer
...

Container Registry storage driver Copy Section

You can configure the Container Registry to use a different storage backend by configuring a different storage driver. By default the GitLab Container Registry is configured to use the filesystem driver, which makes use of storage path configuration. These configurations will all be done in the registry container.

The different supported drivers are:

Read more about the individual driver's config options in the
Docker Registry docs.

Warning GitLab will not backup Docker images that are not stored on the filesystem. Remember to enable backups with your object storage provider if desired.

If you use filesystem as storage driver you need to mount the path from GITLAB_REGISTRY_DIR of the GitLab container in the registry container. So both container can access the registry data.
If you don't change GITLAB_REGISTRY_DIR you will find your registry data in the mounted volume from the GitLab Container under ./gitlab/shared/registry. This don't need to be separated mounted because ./gitlab is already mounted in the GitLab Container. If it will be mounted separated the whole restoring process of GitLab backup won't work because gitlab try to create an folder under ./gitlab/shared/registry /GITLAB_REGISTRY_DIR and GitLab can't delete/remove the mount point inside the container so the restoring process of the backup will fail.
An example how it works is in the docker-compose.

Example for Amazon Simple Storage Service (s3)

If you want to configure your registry via /etc/docker/registry/config.yml your storage part should like this snippet below.

storage:
  s3:
    accesskey: 'AKIAKIAKI'
    secretkey: 'secret123'
    bucket: 'gitlab-registry-bucket-AKIAKIAKI'
  cache:
    blobdescriptor: inmemory
  delete:
    enabled: true

...
 registry:
    restart: always
    image: registry:2.8.3
    volumes:
     - ./certs:/certs
    environment:
    - REGISTRY_LOG_LEVEL=info
    - REGISTRY_AUTH_TOKEN_REALM=https://gitlab.example.com:10080/jwt/auth
    - REGISTRY_AUTH_TOKEN_SERVICE=container_registry
    - REGISTRY_AUTH_TOKEN_ISSUER=gitlab-issuer
    - REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE=/certs/registry-auth.crt
    - REGISTRY_STORAGE_S3_ACCESSKEY=AKIAKIAKI
    - REGISTRY_STORAGE_S3_SECRETKEY=secret123
    - REGISTRY_STORAGE_S3_BUCKET=gitlab-registry-bucket-AKIAKIAKI
    - REGISTRY_CACHE_BLOBDESCRIPTOR=inmemory
    - REGISTRY_STORAGE_DELETE_ENABLED=true

Generally for more information about the configuration of the registry container you can find it under registry configuration.

Storage limitations Copy Section

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

Maintenance Copy Chapter

If you use another storage configuration than filesystem it will have no impact on your Maintenance workflow.

Creating Backups Copy Section

Creating Backups is the same like without a container registry. I would recommend to stop your registry container.

docker stop registry gitlab && docker rm registry gitlab

Execute the rake task with a removeable container.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:19.2.2 app:rake gitlab:backup:create

Restoring Backups Copy Section

GitLab also defines a rake task to restore a backup.

Before performing a restore make sure the container is stopped and removed to avoid container name conflicts.

docker stop registry gitlab && docker rm registry gitlab

Execute the rake task to restore a backup. Make sure you run the container in interactive mode -it.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:19.2.2 app:rake gitlab:backup:restore

The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.

To avoid user interaction in the restore operation, specify the timestamp of the backup using the BACKUP argument to the rake task.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:19.2.2 app:rake gitlab:backup:restore BACKUP=1417624827

Upgrading from an existing GitLab installation Copy Chapter

If you want enable this feature for an existing instance of GitLab you need to do the following steps.

• Step 1: Update the docker image.

docker pull sameersbn/gitlab:19.2.2

• Step 2: Stop and remove the currently running image

docker stop gitlab && docker rm gitlab

• Step 3: Create a backup

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:x.x.x app:rake gitlab:backup:create

• Step 4: Create a certs folder
  Create an authentication certificate with Generating certificate for authentication with the registry.

• Step 5: Create an registry instance

Important Notice

Storage of the registry must be mounted from gitlab from GitLab.
GitLab must have the container of the registry storage folder to be able to create and restore backups

docker run --name registry -d \
--restart=always \
-v /srv/gitlab/shared/registry:/registry \
-v ./certs:/certs \
--env 'REGISTRY_LOG_LEVEL=info' \
--env 'REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registry' \
--env 'REGISTRY_AUTH_TOKEN_REALM=http://gitlab.example.com/jwt/auth' \
--env 'REGISTRY_AUTH_TOKEN_SERVICE=container_registry' \
--env 'REGISTRY_AUTH_TOKEN_ISSUER=gitlab-issuer' \
--env 'REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE=/certs/registry-auth.crt' \
--env 'REGISTRY_STORAGE_DELETE_ENABLED=true' \
registry:2.8.3

• Step 6: Start the image

docker run --name gitlab -d [PREVIOUS_OPTIONS] \
-v /srv/gitlab/certs:/certs \
--env 'SSL_REGISTRY_CERT_PATH=/certs/registry.crt' \
--env 'SSL_REGISTRY_KEY_PATH=/certs/registry.key' \
--env 'GITLAB_REGISTRY_ENABLED=true' \
--env 'GITLAB_REGISTRY_HOST=registry.gitlab.example.com' \
--env 'GITLAB_REGISTRY_API_URL=http://registry:5000/' \
--env 'GITLAB_REGISTRY_CERT_PATH=/certs/registry-auth.crt' \
--env 'GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key' \
--link registry:registry
sameersbn/gitlab:19.2.2

Docker Swarm Traefik Registry Copy Section

Docker Swarm mode deployment

Here's a guide to deploy GitLab with:

• Docker Swarm mode for cluster management and orchestration.
• Docker Registry with HTTPS, TLS (SSL) handled automatically, using GitLab credentials and integration with GitLab CI.
• Traefik proxy to handle domain based redirection, HTTPS communication and automatic certificate generation with Let's encrypt. You don't need to build a custom Nginx proxy or anything similar, it's all handled by Traefik.
• Automatic generation and configuration of GitLab / Registry internal communication certificates.

Set up Docker Swarm Copy Chapter

Set up a Docker Swarm mode cluster with a main global Traefik load balancer following the guide at DockerSwarm.rocks.

It will take you less than 20 minutes to follow it to deploy a cluster (of one or more machines) and have it ready for the next steps.

Configure DNS records Copy Chapter

Configure your DNS domain records to point one subdomain for your GitLab instance and one subdomain for the Docker Registry to the new server.

For example, a DNS A record for gitlab.example.com and a DNS A record for registry.example.com.

If you have a cluster with several nodes, make sure those DNS records point to the IP of the node that will host the gitlab and registry services.

This is because gitlab has to listen on port 22 for Git to work, but we will configure it to make it listen on port 22 only on the server that has GitLab.

That way, if you have other servers in your cluster, you won't have to change the default SSH port of all of them.

Modify the server SSH port Copy Chapter

As by default Git uses the same SSH port 22, and you want your GitLab container to use that port, modify your server SSH configuration to use a different port. This guide will assume you will use port 2222 for your server SSH and port 22 for your GitLab.

Connect to your remote server as normally, e.g.:

ssh [email protected]

Create a backup of your SSH config file:

cp /etc/ssh/sshd_config /etc/ssh/sshd_config.backup

Modify your SSH config.

Warning: if something is broken after modifying the SSH configuration, you could lock yourself out of the server.

You need to have a line Port 2222 and make sure there's no line Port 22.

You can use this command to do it automatically, it will check for a line with Port 22 or #Port 22 and replace it with Port 2222.

sed -i 's|^#\?Port 22$|Port 2222|' /etc/ssh/sshd_config

Or you can modify it with nano by hand, with:

nano /etc/ssh/sshd_config

Confirm that there's a single line with Port 2222 with:

grep "^Port" /etc/ssh/sshd_config

Then restart the SSH server:

systemctl restart sshd.service

Warning: at this point, if you lose your connection and something was wrong in the configuration, you could lock yourself out of the server. Run the following steps in a new terminal session, without closing the existing one, so that, if something was wrong, you can use the current session to edit the configurations, revert them, and restart the SSH service, before being locked out.

In a different terminal session, without closing the existing one, try connecting with SSH to your server using the new port, e.g.:

ssh -p 2222 [email protected]

If you get connected to the remote server normally, everything is working correctly.

Download the Docker Compose stack file Copy Chapter

• Download the Docker Compose stack file:

curl -L https://raw.githubusercontent.com/sameersbn/docker-gitlab/master/docker-compose.swarm.yml -o docker-compose.swarm.yml

Set environment variables Copy Chapter

Set and export the environment variables GITLAB_HOST and REGISTRY_HOST to the subdomains you configured.

For example:

export GITLAB_HOST=gitlab.example.com
export REGISTRY_HOST=registry.example.com

You will use the domain for GITLAB_HOST to access GitLab in your browser and to commit and push with Git.

And you will use the domain for REGISTRY_HOST to store, push, and pull Docker images, e.g.:

docker pull registry.example.com/mygroup/myproject/imagename:sometag

These environment variables will be used by the file docker-compose.swarm.yml.

They are used inside of the stacks and are also used to configure the domains for the Traefik load balancer. Because of that, you need to export them for them to be available when deploying the stack.

Other environment variables Copy Chapter

There are many additional environment variables with different configurations.

Read the main README for all the options.

For Registry specific options and details, check the main GitLab Registry documentation in this repo.

You can configure them by editing de file docker-compose.swarm.yml.

You can do it in the command line with a program like nano, e.g.:

nano docker-compose.swarm.yml

Set other environment variables Copy Chapter

If you want anyone to sign up instead of only people with invitation, change GITLAB_SIGNUP_ENABLED to true:

export GITLAB_SIGNUP_ENABLED=true

There are several environment variables that require random strings for keys and passwords.

For the sections that require generating random strings for keys and passwords, each time, run the following command and copy the output:

openssl rand -hex 32
# Outputs something like: 99d3b1f01aa639e4a76f4fc281fc834747a543720ba4c8a8648ba755aef9be7f

You can copy it and set it in the file like:

- GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alphanumeric-string
- GITLAB_SECRETS_SECRET_KEY_BASE=long-and-random-alphanumeric-string
- GITLAB_SECRETS_OTP_KEY_BASE=long-and-random-alphanumeric-string
- GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE=long-and-random-alphanumeric-string

There are several other settings that you might want to configure, like email accounts for notifications, SMTP credentials to send emails, etc.

Copy the file Copy Chapter

If you modified the file locally, make sure you copy it to your remote server, e.g.:

scp -P 2222 docker-compose.swarm.yml [email protected]:/root/

and connect via SSH to your remote server, e.g.:

ssh -p 2222 [email protected]

If you modified the file locally and then connected to your server later, make sure you export the environment variables GITLAB_HOST and REGISTRY_HOST that are needed even if you modified the Docker Compose file (as those are used in the Traefik labels).

About volumes, labels, and constraints Copy Chapter

Because the Docker Swarm cluster may have more than one single node (machine) in the cluster, we need to make sure that the services that need to save and read files from volumes are always deployed to the same node.

For example, the service for redis uses a volume, you can check it on the docker-compose.swarm.yml file:

volumes:
    - redis-data:/var/lib/redis:Z

To make sure redis is always deployed to the same node that contains the same volume redis-data, we have a constraint:

deploy:
      placement:
        constraints:
          - node.labels.gitlab.redis-data == true

This tells Docker that the service redis should be deployed to a Docker node (a machine in the cluster) with the label node.labels.gitlab.redis-data=true.

Then we can make one node (only one) have this label, and Docker Swarm will always deploy the redis service to the same node. That way, the service will keep reading the same volume every time. Even if you re-deploy or upgrade the stack.

Add constraint labels Copy Chapter

Now we are going to add the needed labels to satisfy those constraints, to make sure the volumes work correctly.

• Connect to a manager node in your Docker Swarm cluster. It could be the same server that will run GitLab, or it could be a different one.

• If you are deploying the stack in the same current manager node, get its node ID and store it in an environment variable:

export NODE_ID=$(docker info -f '{{.Swarm.NodeID}}')

• Otherwise, you can check the current available nodes with:

$ docker node ls

ID                            HOSTNAME             STATUS   AVAILABILITY   MANAGER STATUS   ENGINE VERSION
m48gz5e8ucmk59af4m6enmnaz *   dog.example.com      Ready    Active         Leader           19.03.9
4w456u9lnanau629v3y456k9d     cat.example.com      Ready    Active                          19.03.9
mue36qqwqnzrqt4iqi0yyd6ie     gitlab.example.com   Ready    Active                          19.03.9

And select the node where you want to deploy the main gitlab service. In this example, in the node that has a HOSTNAME with value gitlab.example.com, with node ID mue36qqwqnzrqt4iqi0yyd6ie.

So, you could export that environment variable using the node ID with something like:

export NODE_ID=mue36qqwqnzrqt4iqi0yyd6ie

• Create a label in that node, so that the service gitlab and registry are always deployed to the same node and use the same volumes:

docker node update --label-add gitlab.certs-data=true $NODE_ID

We need to make sure gitlab and registry are deployed on the same node because they share the same volume with the TLS certificates generated by gitlab.

Now create the label for redis. You could use another node in your cluster if you have more than one, for simplicity we are going to use the same node, e.g.:

docker node update --label-add gitlab.redis-data=true $NODE_ID

And add the label for postgres:

docker node update --label-add gitlab.postgresql-data=true $NODE_ID

Note: you only have to set those labels once. Not every time you want to re-deploy your stack.

Deploy the stack Copy Chapter

Now, having the labels set in the Docker nodes, and the environment variables exported, you can deploy your stack:

docker stack deploy --compose-file docker-compose.swarm.yml gitlab

Note: the environment variables GITLAB_HOST and REGISTRY_HOST have to be available every time to deploy the stack. But the node labels can be set only once, the first time you deploy.

You can check the status of the deployment with:

docker stack ps gitlab

Or check the logs, for example for the service gitlab_gitlab:

docker service logs gitlab_gitlab

Internal certificates Copy Chapter

GitLab and the Docker Registry have public facing HTTPS certificates generated with Let's Encrypt for each one. But to communicate between themselves they use an additional self-signed certificate.

To tell GitLab to generate those self-signed certificates for the internal communication with GitLab, the gitlab service has an environment variable:

- GITLAB_REGISTRY_GENERATE_INTERNAL_CERTIFICATES=true

GitLab will generate the certificates and store them in the location given by:

- GITLAB_REGISTRY_KEY_PATH=/certs/registry.key

And that location, /certs, is mounted as a named volume:

volumes:
    - gitlab-data:/home/git/data:Z
    - certs-data:/certs

So, the self-signed certificates will be generated inside the named volume gitlab-certs.

And the Registry also has that named volume mounted:

volumes:
      - registry-data:/registry
      - certs-data:/certs

And the Registry is configured to look for the certificate in that same location that GitLab used to generate the certificate:

- REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE=/certs/registry.crt

GitLab Runner in Docker Copy Chapter

If you use GitLab and want to integrate Continuous Integration / Continuous Deployment, you can follow this section to install the GitLab runner.

You should create the runner using Docker standalone instead of in Docker Swarm mode, as you need the configurations to persist, and in Docker Swarm mode, the container could be deployed to a different server and you would lose those configurations.

Testing and Deployment Copy Section

For testing, the GitLab runner can run in any node.

But if you want to deploy another runner for deployment (or use the same one), it has to run on a manager node in the Docker Swarm cluster.

Create the GitLab Runner in Docker standalone mode Copy Section

To install a GitLab runner in a standalone Docker run:

docker run -d \
    --name gitlab-runner \
    --restart always \
    -v gitlab-runner:/etc/gitlab-runner \
    -v /tmp/builds:/tmp/builds \
    -v /var/run/docker.sock:/var/run/docker.sock \
    gitlab/gitlab-runner:latest

Then, enter into that container:

docker exec -it gitlab-runner bash

Install the GitLab Runner Copy Section

• Go to the GitLab "Admin Area -> Runners" section.
• Get the URL and create a variable with it in the bash session inside of your Runner's Docker container, e.g.:

export GITLAB_URL=https://gitlab.example.com/

• Get the registration token and create a variable in the bash session inside of your Runner's Docker container, e.g.:

export GITLAB_TOKEN=WYasdfJp4sdfasdf1234

• Run the next command editing the name and tags as you need, you can also edit them later in the web user interface.

gitlab-runner \
    register -n \
    --name "Docker Runner" \
    --executor docker \
    --locked false \
    --access-level not_protected \
    --builds-dir /tmp/builds \
    --docker-image docker:latest \
    --docker-volumes /tmp/builds:/tmp/builds \
    --docker-volumes /var/run/docker.sock:/var/run/docker.sock \
    --url $GITLAB_URL \
    --registration-token $GITLAB_TOKEN \
    --tag-list dog-cat-cluster,stag,prod

• You can edit the runner more from the GitLab admin section.

Exposing Ssh Port Copy Section

Exposing ssh port in dockerized gitlab-ce

This is how to expose this internal ssh port without affecting the existing ssh port on the host server:

• use this configuration script: ../contrib/expose-gitlab-ssh-port.sh
• see implementation example in Vagrant: harobed/docker-gitlab-vagrant-test
• more information, see « Exposing ssh port in dockerized gitlab-ce » post

Keycloak Idp Copy Section

Integrate Keycloak as an IDP with GitLab

In this document, we will explain how to set up Keycloak and integrate it into GitLab.

Setting up Keycloak Copy Chapter

First, you need a client in Keycloak to authenticate with GitLab. You can start Keycloak by running docker-compose up -d keycloak.

When Keycloak is running, log in using the Administration console. You can visit the Keycloak on the local IP of your laptop.

Next, create a client.

Fill in the following variables:

Make access type confidential and enable service accounts and authorization.

Next, click save, get the client secret generated by Keycloak and start filling out the variables for GitLab in the docker-compose file.

Set the following in the docker-compose file:

- OAUTH2_GENERIC_APP_SECRET=<your-client-secret>
    - OAUTH2_GENERIC_CLIENT_SITE=http://<your-ip-address>:10081
    - OAUTH2_GENERIC_CLIENT_USER_INFO_URL=http://<your-ip-address>:10081/auth/realms/master/protocol/openid-connect/userinfo
    - OAUTH2_GENERIC_CLIENT_AUTHORIZE_URL=http://<your-ip-address>:10081/auth/realms/master/protocol/openid-connect/auth
    - OAUTH2_GENERIC_CLIENT_TOKEN_URL=http://<your-ip-address>:10081/auth/realms/master/protocol/openid-connect/token
    - OAUTH2_GENERIC_CLIENT_END_SESSION_ENDPOINT=http://<your-ip-address>:10081/auth/realms/master/protocol/openid-connect/logout

<your-ip-address> is the IP address of your keycloak. For this example this would be your IP address, but if your Keycloak existed elsewhere for your deployment <your-ip-address> would be different as would the port and the realm.

The following must also be configured:

- OAUTH2_GENERIC_USER_UID='preferred_username'
    - OAUTH2_GENERIC_USER_NAME='name'
    - OAUTH2_GENERIC_USER_EMAIL='email'

The values will be different for your deployment. Navigate Keycloak's UI, select Clients, click [your client], then open the Client Scopes tab, then open Evaluate sub-tab, enter a username you know in the User field, select the match, then Generate Access Token to see the values you need to configure.

Also, make sure the following variables are filled in the docker-compose file:

- GITLAB_HOST='<your-ip-address>'
    ...
    - OAUTH_ENABLED=true
    - OAUTH_AUTO_SIGN_IN_WITH_PROVIDER=Keycloak
    - OAUTH_ALLOW_SSO=Keycloak
    - OAUTH_BLOCK_AUTO_CREATED_USERS=false
    - OAUTH_AUTO_LINK_LDAP_USER=false
    - OAUTH_AUTO_LINK_SAML_USER=false

<your-ip-address> is the IP address of your GitLab for this example this would be the your IP address, but if your GitLab was to be proxied or deployed elsewhere <your-ip-address> would be another value appropriate for your deployment.

GitLab does not allow login from users in Keycloak with an empty email or name. To prevent this, you can create a new user in Keycloak or you can add email and name for the admin account.

Visit the Users tab and click on View all users to modify the Admin user.

Modify the Email, First name and Last Name fields.

Deploy GitLab, Redis and PostgreSQL by running the following command: docker-compose up -d gitlab redis postgresql.

You can now login on the local GitLab instance with with Keycloak on your local IP.

S3 Compatible Storage Copy Section

GitLab Backup to s3 compatible storage

Enables automatic backups to self-hosted s3 compatible storage like minio (https://minio.io/) and others.
This is an extend of AWS Remote Backups.

As explained in doc.gitlab.com, it uses Fog library and the module fog-aws. More details on s3 supported parameters

• GitLab Backup to s3 compatible storage
  • Available Parameters
  • Installation
    • Docker Compose
    • Creating Backups
    • Restoring Backups

Available Parameters Copy Chapter

Here is an example of all configuration parameters that can be used in the GitLab container.

...
gitlab:
    ...
    environment:
    - AWS_BACKUPS=true
    - AWS_BACKUP_ENDPOINT='http://minio:9000'
    - AWS_BACKUP_ACCESS_KEY_ID=minio
    - AWS_BACKUP_SECRET_ACCESS_KEY=minio123
    - AWS_BACKUP_BUCKET=docker
    - AWS_BACKUP_MULTIPART_CHUNK_SIZE=104857600

where:

For more info look at Available Configuration Parameters.

A minimum set of these parameters are required to use the s3 compatible storage:

...
gitlab:
    environment:
    - AWS_BACKUPS=true
    - AWS_BACKUP_ENDPOINT='http://minio:9000'
    - AWS_BACKUP_ACCESS_KEY_ID=minio
    - AWS_BACKUP_SECRET_ACCESS_KEY=minio123
    - AWS_BACKUP_BUCKET=docker
...

Installation Copy Chapter

Starting a fresh installation with GitLab would be like the docker-compose file.

Docker Compose Copy Section

This is an example with minio.

/* Detailed source-code truncated for AI context efficiency. */

Creating Backups Copy Section

Execute the rake task with a removeable container.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:8.16.4 app:rake gitlab:backup:create

Restoring Backups Copy Section

Execute the rake task to restore a backup. Make sure you run the container in interactive mode -it.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:8.16.4 app:rake gitlab:backup:restore

The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.

To avoid user interaction in the restore operation, specify the timestamp of the backup using the BACKUP argument to the rake task.

docker run --name gitlab -it --rm [OPTIONS] \
    sameersbn/gitlab:8.16.4 app:rake gitlab:backup:restore BACKUP=1417624827

Changelog Copy Section

Changelog

This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://
gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in GitLab.

19.2.2 Copy Chapter

• gitlab: upgrade CE to v19.2.2
• gitaly: upgrade to v19.2.2
• gitlab-pages: upgrade to v19.2.2
• rubygems: upgrade to v4.0.18
• ubuntu: upgrade to noble-20260730.1

19.2.1 Copy Chapter

• gitlab: upgrade CE to v19.2.1
• gitaly: upgrade to v19.2.1
• gitlab-pages: upgrade to v19.2.1
• rubygems: upgrade to v4.0.17

19.2.0 Copy Chapter

• gitlab: upgrade CE to v19.2.0
• gitaly: upgrade to v19.2.0
• gitlab-pages: upgrade to v19.2.0
• gitlab-shell: upgrade to v14.56.1
• ruby: upgrade to v3.3.12
• rubygems: upgrade to v4.0.16

19.1.2 Copy Chapter

• gitlab: upgrade CE to v19.1.2
• gitaly: upgrade to v19.1.2
• gitlab-pages: upgrade to v19.1.2
• golang: upgrade to v1.26.4
• rubygems: upgrade to v4.0.15
• ubuntu: upgrade to noble-20260610

19.1.1 Copy Chapter

• gitlab: upgrade CE to v19.1.1
• gitaly: upgrade to v19.1.1
• gitlab-pages: upgrade to v19.1.1

19.1.0 Copy Chapter

• gitlab: upgrade CE to v19.1.0
• gitaly: upgrade to v19.1.0
• gitlab-pages: upgrade to v19.1.0
• gitlab-shell: upgrade to v14.54.0

19.0.2 Copy Chapter

• gitlab: upgrade CE to v19.0.2
• gitaly: upgrade to v19.0.2
• gitlab-pages: upgrade to v19.0.2
• golang: upgrade to v1.26.4
• rubygems: upgrade to v4.0.14
• ubuntu: upgrade to noble-20260509.1

19.0.1 Copy Chapter

• gitlab: upgrade CE to v19.0.1
• gitaly: upgrade to v19.0.1
• gitlab-pages: upgrade to v19.0.1

19.0.0 Copy Chapter

Important note: In GitLab 19.0 and later, PostgreSQL 17 is the minimum supported version.

• gitlab: upgrade CE to v19.0.0
• gitaly: upgrade to v19.0.0
• gitlab-pages: upgrade to v19.0.0
• gitlab-shell: upgrade to v14.51.0
• rubygems: upgrade to v4.0.12
• postgresql: upgrade to postgresql 17

18.11.3 Copy Chapter

• gitlab: upgrade CE to v18.11.3
• gitaly: upgrade to v18.11.3
• gitlab-pages: upgrade to v18.11.3
• golang: upgrade to v1.26.3

18.11.2 Copy Chapter

• gitlab: upgrade CE to v18.11.2
• gitaly: upgrade to v18.11.2
• gitlab-pages: upgrade to v18.11.2
• rubygems: upgrade to v4.0.11

18.11.1 Copy Chapter

• gitlab: upgrade CE to v18.11.1
• gitaly: upgrade to v18.11.1
• gitlab-pages: upgrade to v18.11.1

18.11.0 Copy Chapter

• gitlab: upgrade CE to v18.11.0
• gitaly: upgrade to v18.11.0
• gitlab-pages: upgrade to v18.11.0
• gitlab-shell: upgrade to v14.49.0
• golang: upgrade to v1.26.2
• ubuntu: upgrade to noble-20260410

18.10.3 Copy Chapter

• gitlab: upgrade CE to v18.10.3
• gitaly: upgrade to v18.10.3
• gitlab-pages: upgrade to v18.10.3
• golang: upgrade to v1.25.9
• ruby: upgrade to v3.2.11
• rubygems: upgrade to v4.0.10
• ubuntu: upgrade to noble-20260324

18.10.1 Copy Chapter

• gitlab: upgrade CE to v18.10.1
• gitaly: upgrade to v18.10.1
• gitlab-pages: upgrade to v18.10.1

18.10.0 Copy Chapter

• gitlab: upgrade CE to v18.10.0
• gitaly: upgrade to v18.10.0
• gitlab-pages: upgrade to v18.10.0
• gitlab-shell: upgrade to v14.47.0
• rubygems: upgrade to v4.0.9
• ubuntu: upgrade to noble-20260217

18.9.2 Copy Chapter

• gitlab: upgrade CE to v18.9.2
• gitaly: upgrade to v18.9.2
• gitlab-pages: upgrade to v18.9.2
• golang: upgrade to v1.25.8
• rubygems: upgrade to v4.0.8

18.9.1 Copy Chapter

• gitlab: upgrade CE to v18.9.1
• gitaly: upgrade to v18.9.1
• gitlab-pages: upgrade to v18.9.1

18.9.0 Copy Chapter

• gitlab: upgrade CE to v18.9.0
• gitaly: upgrade to v18.9.0
• gitlab-pages: upgrade to v18.9.0
• gitlab-shell: upgrade to v14.45.6
• ruby: upgrade to v3.3.10
• ubuntu: upgrade to noble-20260210.1

18.8.4 Copy Chapter

• gitlab: upgrade CE to v18.8.4
• gitaly: upgrade to v18.8.4
• gitlab-pages: upgrade to v18.8.4
• golang: upgrade to v1.25.7
• rubygems: upgrade to v4.0.6

18.8.3 Copy Chapter

• gitlab: upgrade CE to v18.8.3
• gitaly: upgrade to v18.8.3
• gitlab-pages: upgrade to v18.8.3

18.8.2 Copy Chapter

• gitlab: upgrade CE to v18.8.2
• gitaly: upgrade to v18.8.2
• gitlab-pages: upgrade to v18.8.2

18.8.1 Copy Chapter

• gitlab: upgrade CE to v18.8.1
• gitaly: upgrade to v18.8.1
• gitlab-pages: upgrade to v18.8.1

18.8.0 Copy Chapter

• gitlab: upgrade CE to v18.8.0
• gitaly: upgrade to v18.8.0
• gitlab-pages: upgrade to v18.8.0
• golang: upgrade to v1.24.12
• ruby: upgrade to v3.2.10
• ubuntu: upgrade to noble-20260113

18.7.1 Copy Chapter

• gitlab: upgrade CE to v18.7.1
• gitaly: upgrade to v18.7.1
• gitlab-pages: upgrade to v18.7.1

18.7.0 Copy Chapter

• gitlab: upgrade CE to v18.7.0
• gitaly: upgrade to v18.7.0
• gitlab-pages: upgrade to v18.7.0
• gitlab-shell: upgrade to v14.45.5

18.6.2 Copy Chapter

• gitlab: upgrade CE to v18.6.2
• gitaly: upgrade to v18.6.2
• gitlab-pages: upgrade to v18.6.2
• golang: upgrade to v1.24.11

18.6.1 Copy Chapter

• gitlab: upgrade CE to v18.6.1
• gitaly: upgrade to v18.6.1
• gitlab-pages: upgrade to v18.6.1

18.6.0 Copy Chapter

• gitlab: upgrade CE to v18.6.0
• gitaly: upgrade to v18.6.0
• gitlab-pages: upgrade to v18.6.0
• ubuntu: upgrade to noble-20251013

18.5.2 Copy Chapter

• gitlab: upgrade CE to v18.5.2
• gitaly: upgrade to v18.5.2
• gitlab-pages: upgrade to v18.5.2
• golang: upgrade to v1.24.10

18.5.1 Copy Chapter

• gitlab: upgrade CE to v18.5.1
• gitaly: upgrade to v18.5.1
• gitlab-pages: upgrade to v18.5.1

18.5.0 Copy Chapter

• gitlab: upgrade CE to v18.5.0
• gitaly: upgrade to v18.5.0
• gitlab-pages: upgrade to v18.5.0
• gitlab-shell: upgrade to v14.45.3
• golang: upgrade to v1.24.9
• ubuntu: upgrade to noble-20251001

18.4.2 Copy Chapter

• gitlab: upgrade CE to v18.4.2
• gitaly: upgrade to v18.4.2
• gitlab-pages: upgrade to v18.4.2
• golang: upgrade to v1.24.8
• ubuntu: upgrade to noble-20250925

18.4.1 Copy Chapter

• gitlab: upgrade CE to v18.4.1
• gitaly: upgrade to v18.4.1
• gitlab-pages: upgrade to v18.4.1
• ubuntu: upgrade to noble-20250910

18.4.0 Copy Chapter

• gitlab: upgrade CE to v18.4.0
• gitaly: upgrade to v18.4.0
• gitlab-pages: upgrade to v18.4.0
• ubuntu: upgrade to noble-20250910

18.3.2 Copy Chapter

• gitlab: upgrade CE to v18.3.2
• gitaly: upgrade to v18.3.2
• gitlab-pages: upgrade to v18.3.2
• gitlab-shell: upgrade to v14.45.2
• golang: upgrade to v1.24.7
• rubygems: upgrade to v3.7.2
• ubuntu: upgrade to noble-20250805

18.3.1 Copy Chapter

• gitlab: upgrade CE to v18.3.1
• gitaly: upgrade to v18.3.1
• gitlab-pages: upgrade to v18.3.1

18.3.0 Copy Chapter

• gitlab: upgrade CE to v18.3.0
• gitaly: upgrade to v18.3.0
• gitlab-pages: upgrade to v18.3.0

18.2.4 Copy Chapter

• gitlab: upgrade CE to v18.2.4
• gitaly: upgrade to v18.2.4
• gitlab-pages: upgrade to v18.2.4
• gitlab-shell: upgrade to v14.44.0

18.2.2 Copy Chapter

• gitlab: upgrade CE to v18.2.2
• gitaly: upgrade to v18.2.2
• gitlab-pages: upgrade to v18.2.2
• golang: upgrade to v1.24.6
• ubuntu: upgrade to noble-20250716

18.2.1 Copy Chapter

• gitlab: upgrade CE to v18.2.1
• gitaly: upgrade to v18.2.1
• gitlab-pages: upgrade to v18.2.1
• ruby: upgrade to v3.2.9
• rubygems: upgrade to v3.7.1

18.2.0 Copy Chapter

• gitlab: upgrade CE to v18.2.0
• gitaly: upgrade to v18.2.0
• gitlab-pages: upgrade to v18.2.0
• gitlab-shell: upgrade to v14.43.0
• rubygems: upgrade to v3.7.0
• ubuntu: upgrade to noble-20250714

18.1.2 Copy Chapter

• gitlab: upgrade CE to v18.1.2
• gitaly: upgrade to v18.1.2
• gitlab-pages: upgrade to v18.1.2
• golang: upgrade to v1.24.5
• ubuntu: upgrade to noble-20250619

18.1.1 Copy Chapter

• gitlab: upgrade CE to v18.1.1
• gitaly: upgrade to v18.1.1
• gitlab-pages: upgrade to v18.1.1

18.1.0 Copy Chapter

• gitlab: upgrade CE to v18.1.0
• gitaly: upgrade to v18.1.0
• gitlab-pages: upgrade to v18.1.0

18.0.2 Copy Chapter

• gitlab: upgrade CE to v18.0.2
• gitaly: upgrade to v18.0.2
• gitlab-pages: upgrade to v18.0.2
• golang: upgrade to v1.24.4
• ubuntu: upgrade to noble-20250529

18.0.1 Copy Chapter

• gitlab: upgrade CE to v18.0.1
• gitaly: upgrade to v18.0.1
• gitlab-pages: upgrade to v18.0.1
• gitlab-shell: upgrade to v14.42.0

18.0.0 Copy Chapter

• gitlab: upgrade CE to v18.0.0
• gitaly: upgrade to v18.0.0
• gitlab-pages: upgrade to v18.0.0
• redis: upgrade to v7
• rubygems: upgrade to v3.6.9
• ubuntu: upgrade to noble-20250415.1

17.11.2 Copy Chapter

• gitlab: upgrade CE to v17.11.2
• gitaly: upgrade to v17.11.2
• gitlab-pages: upgrade to v17.11.2
• golang: upgrade to v1.24.3
• ubuntu: upgrade to jammy-20250415.1

17.11.1 Copy Chapter

• gitlab: upgrade CE to v17.11.1
• gitaly: upgrade to v17.11.1
• gitlab-pages: upgrade to v17.11.1
• rubygems: upgrade to v3.6.8

17.11.0 Copy Chapter

• gitlab: upgrade CE to v17.11.0
• gitaly: upgrade to v17.11.0
• gitlab-pages: upgrade to v17.11.0

17.10.4 Copy Chapter

• gitlab: upgrade CE to v17.10.4
• gitaly: upgrade to v17.10.4
• gitlab-pages: upgrade to v17.10.4
• ubuntu: upgrade to jammy-20250404

17.10.3 Copy Chapter

• gitlab: upgrade CE to v17.10.3
• gitaly: upgrade to v17.10.3
• gitlab-pages: upgrade to v17.10.3
• golang: upgrade to v1.24.2
• ruby: upgrade to v3.2.8

17.10.1 Copy Chapter

• gitlab: upgrade CE to v17.10.1
• gitaly: upgrade to v17.10.1
• gitlab-pages: upgrade to v17.10.1

17.10.0 Copy Chapter

• gitlab: upgrade CE to v17.10.0
• gitaly: upgrade to v17.10.0
• gitlab-pages: upgrade to v17.10.0
• golang: upgrade to v1.24.1
• rubygems: upgrade to v3.6.6

17.9.2 Copy Chapter

• gitlab: upgrade CE to v17.9.2
• gitaly: upgrade to v17.9.2
• gitlab-pages: upgrade to v17.9.2

17.9.1 Copy Chapter

• gitlab: upgrade CE to v17.9.1
• gitaly: upgrade to v17.9.1
• gitlab-pages: upgrade to v17.9.1

17.9.0 Copy Chapter

• gitlab: upgrade CE to v17.9.0
• gitaly: upgrade to v17.9.0
• gitlab-pages: upgrade to v17.9.0
• gitlab-shell: upgrade to v14.40.0
• golang: upgrade to v1.24.0
• rubygems: upgrade to v3.5.23
• ubuntu: upgrade to jammy-20250126

17.8.2 Copy Chapter

• gitlab: upgrade CE to v17.8.2
• gitaly: upgrade to v17.8.2
• gitlab-pages: upgrade to v17.8.2
• golang: upgrade to v1.23.6
• ruby: upgrade to v3.2.7

17.8.1 Copy Chapter

• gitlab: upgrade CE to v17.8.1
• gitaly: upgrade to v17.8.1
• gitlab-pages: upgrade to v17.8.1

17.8.0 Copy Chapter

• gitlab: upgrade CE to v17.8.0
• gitaly: upgrade to v17.8.0
• gitlab-pages: upgrade to v17.8.0

17.7.1 Copy Chapter

• gitlab: upgrade CE to v17.7.1
• gitaly: upgrade to v17.7.1
• gitlab-pages: upgrade to v17.7.1

17.7.0 Copy Chapter

• gitlab: upgrade CE to v17.7.0
• gitaly: upgrade to v17.7.0
• gitlab-pages: upgrade to v17.7.0
• ubuntu: upgrade to jammy-20240911.1
• update healthcheck for postgresql

17.6.3 Copy Chapter

• gitlab: upgrade CE to v17.6.3
• gitaly: upgrade to v17.6.3
• gitlab-pages: upgrade to v17.6.3

17.6.2 Copy Chapter

• gitlab: upgrade CE to v17.6.2
• gitaly: upgrade to v17.6.2
• gitlab-pages: upgrade to v17.6.2

17.6.1 Copy Chapter

• gitlab: upgrade CE to v17.6.1
• gitlab-pages: upgrade to v17.6.1
• gitaly: upgrade to v17.6.1
• golang: upgrade to v1.23.5

17.6.0 Copy Chapter

• gitlab: upgrade CE to v17.6.0
• gitaly: upgrade to v17.6.0
• gitlab-pages: upgrade to v17.6.0

17.5.2 Copy Chapter

• gitlab: upgrade CE to v17.5.2
• gitaly: upgrade to v17.5.2
• gitlab-pages: upgrade to v17.5.2
• golang: upgrade to v1.23.2
• ruby: upgrade to v3.2.6

17.5.1 Copy Chapter

• gitlab: upgrade CE to v17.5.1
• gitaly: upgrade to v17.5.1
• gitlab-pages: upgrade to v17.5.1

17.5.0 Copy Chapter

• gitlab: upgrade CE to v17.5.0
• gitaly: upgrade to v17.5.0
• gitlab-pages: upgrade to v17.5.0
• ubuntu: upgrade to focal-20241011

17.4.2 Copy Chapter

• gitlab: upgrade CE to v17.4.2
• gitaly: upgrade to v17.4.2
• gitlab-pages: upgrade to v17.4.2
• golang: upgrade to v1.23.2
• ubuntu: upgrade to focal-20240918

17.4.1 Copy Chapter

• gitlab: upgrade CE to v17.4.1
• gitaly: upgrade to v17.4.1
• gitlab-pages: upgrade to v17.4.1

17.4.0 Copy Chapter

• gitlab: upgrade CE to v17.4.0
• gitaly: upgrade to v17.4.0
• gitlab-pages: upgrade to v17.4.0
• gitlab-shell: upgrade to v14.39.0

17.3.3 Copy Chapter

• gitlab: upgrade CE to v17.3.3
• gitaly: upgrade to v17.3.3
• gitlab-pages: upgrade to v17.3.3

17.3.2 Copy Chapter

• gitlab: upgrade CE to v17.3.2
• gitaly: upgrade to v17.3.2
• gitlab-pages: upgrade to v17.3.2
• golang: upgrade to v1.23.1

17.3.1 Copy Chapter

• gitlab: upgrade CE to v17.3.1
• gitaly: upgrade to v17.3.1
• gitlab-pages: upgrade to v17.3.1

17.3.0 Copy Chapter

• gitlab: upgrade CE to v17.3.0
• gitaly: upgrade to v17.3.0
• gitlab-pages: upgrade to v17.3.0
• gitlab-shell: upgrade to v14.38.0
• golang: upgrade to v1.23.0

17.2.2 Copy Chapter

• gitlab: upgrade CE to v17.2.2
• gitaly: upgrade to v17.2.2
• gitlab-pages: upgrade to v17.2.2
• golang: upgrade to v1.22.6

17.2.1 Copy Chapter

• gitlab: upgrade CE to v17.2.1
• gitaly: upgrade to v17.2.1
• gitlab-pages: upgrade to v17.2.1
• ruby: upgrade to v3.2.5

17.2.0 Copy Chapter

• gitlab: upgrade CE to v17.2.0
• gitaly: upgrade to v17.2.0
• gitlab-pages: upgrade to v17.2.0
• gitlab-shell: upgrade to v14.37.0

17.1.2 Copy Chapter

• gitlab: upgrade CE to v17.1.2
• gitaly: upgrade to v17.1.2
• gitlab-pages: upgrade to v17.1.2
• golang: upgrade to v1.22.5

17.1.1 Copy Chapter

• gitlab: upgrade CE to v17.1.1
• gitaly: upgrade to v17.1.1
• gitlab-pages: upgrade to v17.1.1

17.1.0 Copy Chapter

• gitlab: upgrade CE to v17.1.0
• gitaly: upgrade to v17.1.0
• gitlab-pages: upgrade to v17.1.0
• gitlab-shell: upgrade to v14.36.0

17.0.2 Copy Chapter

• gitlab: upgrade CE to v17.0.2
• gitaly: upgrade to v17.0.2
• gitlab-pages: upgrade to v17.0.2
• golang: upgrade to v1.22.4
• ubuntu: upgrade to focal-20240530

17.0.1 Copy Chapter

• gitlab: upgrade CE to v17.0.1
• gitaly: upgrade to v17.0.1
• gitlab-pages: upgrade to v17.0.1

17.0.0 Copy Chapter

• gitlab: upgrade CE to v17.0.0
• gitaly: upgrade to v17.0.0
• gitlab-pages: upgrade to v17.0.0
• gitlab-shell: upgrade to v14.35.0

16.11.2 Copy Chapter

• gitlab: upgrade CE to v16.11.2
• gitaly: upgrade to v16.11.2
• gitlab-pages: upgrade to v16.11.2
• golang: upgrade to v1.22.3
• ubuntu: upgrade to focal-20240427

16.11.1 Copy Chapter

• gitlab: upgrade CE to v16.11.1
• gitaly: upgrade to v16.11.1
• gitlab-pages: upgrade to v16.11.1
• ruby: upgrade to v3.2.4
• ubuntu: upgrade to focal-20240416

16.11.0 Copy Chapter

• gitlab: upgrade CE to v16.11.0
• gitaly: upgrade to v16.11.0
• gitlab-pages: upgrade to v16.11.0
• gitlab-shell: upgrade to v14.35.0

16.10.3 Copy Chapter

• gitlab: upgrade CE to v16.10.3
• gitaly: upgrade to v16.10.3
• gitlab-pages: upgrade to v16.10.3
• ubuntu: upgrade to focal-20240410

16.10.2 Copy Chapter

• gitlab: upgrade CE to v16.10.2
• gitaly: upgrade to v16.10.2
• gitlab-pages: upgrade to v16.10.2
• golang: upgrade to v1.22.2

16.10.1 Copy Chapter

• gitlab: upgrade CE to v16.10.1
• gitaly: upgrade to v16.10.1
• gitlab-pages: upgrade to v16.10.1

16.10.0 Copy Chapter

• gitlab: upgrade CE to v16.10.0
• gitaly: upgrade to v16.10.0
• gitlab-pages: upgrade to v16.10.0
• gitlab-shell: upgrade to v14.34.0

16.9.2 Copy Chapter

• gitlab: upgrade CE to v16.9.2
• gitaly: upgrade to v16.9.2
• gitlab-pages: upgrade to v16.9.2
• golang: upgrade to v1.22.1
• ubuntu: upgrade to focal-20240216

16.9.1 Copy Chapter

• gitlab: upgrade CE to v16.9.1
• gitaly: upgrade to v16.9.1
• gitlab-pages: upgrade to v16.9.1

16.9.0 Copy Chapter

• gitlab: upgrade CE to v16.9.0
• gitaly: upgrade to v16.9.0
• gitlab-pages: upgrade to v16.9.0

16.8.2 Copy Chapter

• gitlab: upgrade CE to v16.8.2
• gitaly: upgrade to v16.8.2
• gitlab-pages: upgrade to v16.8.2
• golang: upgrade to v1.22.0
• ubuntu: upgrade to focal-20240123

16.8.1 Copy Chapter

• gitlab: upgrade CE to v16.8.1
• gitaly: upgrade to v16.8.1
• gitlab-pages: upgrade to v16.8.1
• gitlab-shell: upgrade to v14.33.0

16.8.0 Copy Chapter

• gitlab: upgrade CE to v16.8.0
• gitaly: upgrade to v16.8.0
• gitlab-pages: upgrade to v16.8.0

16.7.3 Copy Chapter

• gitlab: upgrade CE to v16.7.3
• gitaly: upgrade to v16.7.3
• gitlab-pages: upgrade to v16.7.3

16.7.2 Copy Chapter

• gitlab: upgrade CE to v16.7.2
• gitaly: upgrade to v16.7.2
• gitlab-pages: upgrade to v16.7.2
• golang: upgrade to v1.21.6

16.7.0 Copy Chapter

• gitlab: upgrade CE to v16.7.0
• gitaly: upgrade to v16.7.0
• gitlab-pages: upgrade to v16.7.0
• gitlab-shell: upgrade to v14.32.0
• ruby: upgrade to v3.1.4

16.6.2 Copy Chapter

• gitlab: upgrade CE to v16.6.2
• gitaly: upgrade to v16.6.2
• gitlab-pages: upgrade to v16.6.2
• golang: upgrade to v1.21.5
• ubuntu: upgrade to focal-20231211

16.6.1 Copy Chapter

• gitlab: upgrade CE to v16.6.1
• gitaly: upgrade to v16.6.1
• gitlab-pages: upgrade to v16.6.1
• ubuntu: upgrade to focal-20231128

16.6.0 Copy Chapter

• gitlab: upgrade CE to v16.6.0
• gitaly: upgrade to v16.6.0
• gitlab-pages: upgrade to v16.6.0
• gitlab-shell: upgrade to v14.30.0
• golang: upgrade to v1.21.4

16.5.1 Copy Chapter

• gitlab: upgrade CE to v16.5.1
• gitaly: upgrade to v16.5.1
• gitlab-pages: upgrade to v16.5.1

16.5.0 Copy Chapter

• gitlab: upgrade CE to v16.5.0
• gitaly: upgrade to v16.5.0
• gitlab-pages: upgrade to v16.5.0
• gitlab-shell: upgrade to v14.29.0
• golang: upgrade to v1.21.3
• ubuntu: upgrade to focal-20231003

16.4.1 Copy Chapter

• gitlab: upgrade CE to v16.4.1
• gitaly: upgrade to v16.4.1
• gitlab-pages: upgrade to v16.4.1

16.4.0 Copy Chapter

• gitlab: upgrade CE to v16.4.0
• gitaly: upgrade to v16.4.0
• gitlab-pages: upgrade to v16.4.0
• gitlab-shell: upgrade to v14.28.0

16.3.4 Copy Chapter

• gitlab: upgrade CE to v16.3.4
• gitaly: upgrade to v16.3.4
• gitlab-pages: upgrade to v16.3.4

16.3.3 Copy Chapter

• gitlab: upgrade CE to v16.3.3
• gitaly: upgrade to v16.3.3
• gitlab-pages: upgrade to v16.3.3

16.3.2 Copy Chapter

• gitlab: upgrade CE to v16.3.2
• gitaly: upgrade to v16.3.2
• gitlab-pages: upgrade to v16.3.2
• golang: upgrade to v1.21.1

16.3.1 Copy Chapter

• gitlab: upgrade CE to v16.3.1
• gitaly: upgrade to v16.3.1
• gitlab-pages: upgrade to v16.3.1

16.3.0 Copy Chapter

• gitlab: upgrade CE to v16.3.0
• gitaly: upgrade to v16.3.0
• gitlab-pages: upgrade to v16.3.0

16.2.4 Copy Chapter

• gitlab: upgrade CE to v16.2.4
• gitaly: upgrade to v16.2.4
• gitlab-pages: upgrade to v16.2.4
• golang: upgrade to v1.21.0

16.2.3 Copy Chapter

• gitlab: upgrade CE to v16.2.3
• gitaly: upgrade to v16.2.3
• gitlab-pages: upgrade to v16.2.3

16.2.2 Copy Chapter

• gitlab: upgrade CE to v16.2.2
• gitaly: upgrade to v16.2.2
• gitlab-pages: upgrade to v16.2.2
• golang: upgrade to v1.20.7
• ubuntu: upgrade to focal-20230801

16.2.1 Copy Chapter

• gitlab: upgrade CE to v16.2.1
• gitaly: upgrade to v16.2.1
• gitlab-pages: upgrade to v16.2.1

16.2.0 Copy Chapter

• gitlab: upgrade CE to v16.2.0
• gitaly: upgrade to v16.2.0
• gitlab-pages: upgrade to v16.2.0
• golang: upgrade to v1.20.6

16.1.2 Copy Chapter

• gitlab: upgrade CE to v16.1.2
• gitaly: upgrade to v16.1.2
• gitlab-pages: upgrade to v16.1.2
• ubuntu: upgrade to focal-20230624

16.1.1 Copy Chapter

• gitlab: upgrade CE to v16.1.1
• gitaly: upgrade to v16.1.1
• gitlab-pages: upgrade to v16.1.1

16.1.0 Copy Chapter

• gitlab: upgrade CE to v16.1.0
• gitaly: upgrade to v16.1.0
• gitlab-pages: upgrade to v16.1.0
• gitlab-shell: upgrade to v14.23.0

16.0.5 Copy Chapter

• gitlab: upgrade CE to v16.0.5
• gitaly: upgrade to v16.0.5
• gitlab-pages: upgrade to v16.0.5
• ubuntu: upgrade to focal-20230605

16.0.4 Copy Chapter

• gitlab: upgrade CE to v16.0.4
• gitaly: upgrade to v16.0.4
• gitlab-pages: upgrade to v16.0.4

16.0.3 Copy Chapter

• gitlab: upgrade CE to v16.0.3
• gitaly: upgrade to v16.0.3
• gitlab-pages: upgrade to v16.0.3

16.0.2 Copy Chapter

• gitlab: upgrade CE to v16.0.2
• gitaly: upgrade to v16.0.2
• gitlab-pages: upgrade to v16.0.2
• golang: upgrade to v1.20.5

16.0.1 Copy Chapter

• gitlab: upgrade CE to v16.0.1
• gitaly: upgrade to v16.0.1
• gitlab-pages: upgrade to v16.0.1

16.0.0 Copy Chapter

• gitlab: upgrade CE to v16.0.0
• gitaly: upgrade to v16.0.0
• gitlab-pages: upgrade to v16.0.0
• gitlab-shell: upgrade to v14.20.0

15.11.5 Copy Chapter

• gitlab: upgrade CE to v15.11.5
• gitaly: upgrade to v15.11.5
• gitlab-pages: upgrade to v15.11.5

15.11.4 Copy Chapter

• gitlab: upgrade CE to v15.11.4
• gitaly: upgrade to v15.11.4
• gitlab-pages: upgrade to v15.11.4

15.11.3 Copy Chapter

• gitlab: upgrade CE to v15.11.3
• gitaly: upgrade to v15.11.3
• gitlab-pages: upgrade to v15.11.3
• ruby: upgrade to v3.0.6

15.11.2 Copy Chapter

• gitlab: upgrade CE to v15.11.2
• gitaly: upgrade to v15.11.2
• gitlab-pages: upgrade to v15.11.2

15.11.1 Copy Chapter

• gitlab: upgrade CE to v15.11.1
• gitaly: upgrade to v15.11.1
• gitlab-pages: upgrade to v15.11.1
• golang: upgrade to v1.20.4

15.11.0 Copy Chapter

• gitlab: upgrade CE to v15.11.0
• gitaly: upgrade to v15.11.0
• gitlab-pages: upgrade to v15.11.0
• ubuntu: upgrade to focal-20230412

15.10.3 Copy Chapter

• gitlab: upgrade CE to v15.10.3
• gitaly: upgrade to v15.10.3
• gitlab-pages: upgrade to v15.10.3

15.10.2 Copy Chapter

• gitlab: upgrade CE to v15.10.2
• gitaly: upgrade to v15.10.2
• gitlab-pages: upgrade to v15.10.2
• golang: upgrade to v1.20.3

15.10.1 Copy Chapter

• gitlab: upgrade CE to v15.10.1
• gitaly: upgrade to v15.10.1
• gitlab-pages: upgrade to v15.10.1
• ruby: upgrade to v2.7.8
• ubuntu: upgrade to focal-20230308

15.10.0 Copy Chapter

• gitlab: upgrade CE to v15.10.0
• gitaly: upgrade to v15.10.0
• gitlab-pages: upgrade to v15.10.0
• gitlab-shell: upgrade to v14.18.0
• ubuntu: upgrade to focal-20230308

15.9.3 Copy Chapter

• gitlab: upgrade CE to v15.9.3
• gitaly: upgrade to v15.9.3
• gitlab-pages: upgrade to v15.9.3
• golang: upgrade to v1.20.2

15.9.2 Copy Chapter

• gitlab: upgrade CE to v15.9.2
• gitaly: upgrade to v15.9.2
• gitlab-pages: upgrade to v15.9.2
• ubuntu: upgrade to focal-20230301

15.9.1 Copy Chapter

• gitlab: upgrade CE to v15.9.1
• gitaly: upgrade to v15.9.1
• gitlab-pages: upgrade to v15.9.1

15.9.0 Copy Chapter

• gitlab: upgrade CE to v15.9.0
• gitaly: upgrade to v15.9.0
• gitlab-pages: upgrade to v15.9.0
• gitlab-shell: upgrade to v14.17.0

15.8.2 Copy Chapter

• gitlab: upgrade CE to v15.8.2
• gitaly: upgrade to v15.8.2
• gitlab-pages: upgrade to v15.8.2
• golang: upgrade to v1.19.6

15.8.1 Copy Chapter

• gitlab: upgrade CE to v15.8.1
• gitaly: upgrade to v15.8.1
• gitlab-pages: upgrade to v15.8.1
• ubuntu: upgrade to focal-20230126

15.8.0-1 Copy Chapter

• ruby: rollback to v2.7.7

15.8.0 Copy Chapter

• gitlab: upgrade CE to v15.8.0
• gitaly: upgrade to v15.8.0
• gitlab-pages: upgrade to v15.8.0
• gitlab-shell: upgrade to v14.15.0
• golang: upgrade to v1.18.10

15.7.5 Copy Chapter

• gitlab: upgrade CE to v15.7.5
• gitaly: upgrade to v15.7.5
• gitlab-pages: upgrade to v15.7.5

15.7.3 Copy Chapter

• gitlab: upgrade CE to v15.7.3
• gitaly: upgrade to v15.7.3
• gitlab-pages: upgrade to v15.7.3

15.7.2 Copy Chapter

• gitlab: upgrade CE to v15.7.2
• gitaly: upgrade to v15.7.2
• gitlab-pages: upgrade to v15.7.2

15.7.1 Copy Chapter

• gitlab: upgrade CE to v15.7.1
• gitaly: upgrade to v15.7.1
• gitlab-pages: upgrade to v15.7.1

15.7.0 Copy Chapter

• gitlab: upgrade CE to v15.7.0
• gitaly: upgrade to v15.7.0
• gitlab-pages: upgrade to v15.7.0
• gitlab-shell: upgrade to v14.14.0
• ruby: upgrade to v3.0.5

15.6.3 Copy Chapter

• gitlab: upgrade CE to v15.6.3
• gitaly: upgrade to v15.6.3
• gitlab-pages: upgrade to v15.6.3
• ubuntu: upgrade to focal-20221130
• ruby: upgrade to v2.7.7
• ruby: upgrade to v3.0.4

15.6.2 Copy Chapter

• gitlab: upgrade CE to v15.6.2
• gitaly: upgrade to v15.6.2

15.6.1 Copy Chapter

• gitlab: upgrade CE to v15.6.1
• gitaly: upgrade to v15.6.1

15.6.0 Copy Chapter

• gitlab: upgrade CE to v15.6.0
• gitaly: upgrade to v15.6.0
• gitlab-shell: upgrade to v14.13.0
• gitlab-pages: upgrade to v1.63.0
• golang: upgrade to v1.18.8

15.5.4 Copy Chapter

• gitlab: upgrade CE to v15.5.4
• gitaly: upgrade to v15.5.4

15.5.3 Copy Chapter

• gitlab: upgrade CE to v15.5.3
• gitaly: upgrade to v15.5.3

15.5.2 Copy Chapter

• gitlab: upgrade CE to v15.5.2
• gitaly: upgrade to v15.5.2
• ubuntu: upgrade to focal-20221019

15.5.1 Copy Chapter

• gitlab: upgrade CE to v15.5.1
• gitaly: upgrade to v15.5.1

15.5.0 Copy Chapter

• gitlab: upgrade CE to v15.5.0
• gitaly: upgrade to v15.5.0
• gitlab-shell: upgrade to v14.12.0

15.4.3 Copy Chapter

• gitlab: upgrade CE to v15.4.3
• gitaly: upgrade to v15.4.3
• ubuntu: upgrade to focal-20220922

15.4.2 Copy Chapter

• gitlab: upgrade CE to v15.4.2
• gitaly: upgrade to v15.4.2

15.4.1 Copy Chapter

• gitlab: upgrade CE to v15.4.1
• gitaly: upgrade to v15.4.1

15.4.0 Copy Chapter

• gitlab: upgrade CE to v15.4.0
• gitaly: upgrade to v15.4.0
• ubuntu: upgrade tofocal-20220826

15.3.3 Copy Chapter

• gitlab: upgrade CE to v15.3.3
• gitaly: upgrade to v15.3.3

15.3.2 Copy Chapter

• gitlab: upgrade CE to v15.3.2
• gitaly: upgrade to v15.3.2

15.3.1 Copy Chapter

• gitlab: upgrade CE to v15.3.1
• gitaly: upgrade to v15.3.1

15.3.0 Copy Chapter

• gitlab: upgrade CE to v15.3.0
• gitaly: upgrade to v15.3.0
• gitlab-shell: upgrade to v14.10.0
• gitlab-pages: upgrade to v1.62.0
• ubuntu: upgrade to focal-20220801

15.2.2 Copy Chapter

• gitlab: upgrade CE to v15.2.2
• gitaly: upgrade to v15.2.2
• golang: upgrade to v1.17.13

15.2.1 Copy Chapter

• gitlab: upgrade CE to v15.2.1
• gitaly: upgrade to v15.2.1
• gitlab-pages: upgrade to v1.61.1

15.2.0 Copy Chapter

• gitlab: upgrade CE to v15.2.0
• gitaly: upgrade to v15.2.0
• gitlab-shell: upgrade to v14.9.0
• gitlab-pages: upgrade to v1.61.0
• golang: upgrade to v1.17.12

15.1.3 Copy Chapter

• gitlab: upgrade CE to v15.1.3
• gitaly: upgrade to v15.1.3

15.1.2 Copy Chapter

• gitlab: upgrade CE to v15.1.2
• gitaly: upgrade to v15.1.2

15.1.1 Copy Chapter

• gitlab: upgrade CE to v15.1.1
• gitaly: upgrade to v15.1.1

15.1.0 Copy Chapter

• gitlab: upgrade CE to v15.1.0
• gitaly: upgrade to v15.1.0
• gitlab-shell: upgrade to v14.7.4
• gitlab-pages: upgrade to v1.59.0

15.0.3 Copy Chapter

• gitlab: upgrade CE to v15.0.3
• gitaly: upgrade to v15.0.3

15.0.2 Copy Chapter

• gitlab: upgrade CE to v15.0.2
• gitaly: upgrade to v15.0.2
• ubuntu: upgrade to focal-20220531

15.0.1 Copy Chapter

• gitlab: upgrade CE to v15.0.1
• gitaly: upgrade to v15.0.1
• golang: upgrade to v1.17.11

15.0.0 Copy Chapter

• gitlab: upgrade CE to v15.0.0
• gitaly: upgrade to v15.0.0
• golang: upgrade to v1.17.10
• gitlab-shell: upgrade to v14.3.0
• gitlab-pages: upgrade to v1.58.0

14.10.3 Copy Chapter

• gitlab: upgrade CE to v14.10.3
• gitaly: upgrade to v14.10.3

14.10.2 Copy Chapter

• gitlab: upgrade CE to v14.10.2
• gitaly: upgrade to v14.10.2
• ubuntu: upgrade to focal-20220426

14.10.1 Copy Chapter

• gitlab: upgrade CE to v14.10.1
• gitaly: upgrade to v14.10.1
• ubuntu: upgrade to focal-20220426

14.10.0 Copy Chapter

• gitlab: upgrade CE to v14.10.0
• gitaly: upgrade to v14.10.0
• gitlab-shell: upgrade to v13.25.1
• ubuntu: upgrade to focal-20220415

14.9.3 Copy Chapter

• gitlab: upgrade CE to v14.9.3
• gitaly: upgrade to v14.9.3
• golang: upgrade to v1.17.9
• ruby: upgrade to v2.7.6
• ubuntu: upgrade to focal-20220404

14.9.2 Copy Chapter

• gitlab: upgrade CE to v14.9.2
• gitaly: upgrade to v14.9.2
• gitlab-pages: upgrade to v1.56.1

14.9.1 Copy Chapter

• gitlab: upgrade CE to v14.9.1
• gitaly: upgrade to v14.9.1

14.9.0 Copy Chapter

• gitlab: upgrade CE to v14.9.0
• gitaly: upgrade to v14.9.0
• gitlab-pages: upgrade to v1.56.0
• gitlab-shell: upgrade to v13.24.0

14.8.4 Copy Chapter

• gitlab: upgrade CE to v14.8.4
• gitaly: upgrade to v14.8.4

14.8.3 Copy Chapter

• gitlab: upgrade CE to v14.8.3
• gitaly: upgrade to v14.8.3
• golang: upgrade to v1.17.8
• ubuntu: upgrade to focal-20220316

14.8.2 Copy Chapter

• gitlab: upgrade CE to v14.8.2
• gitaly: upgrade to v14.8.2

14.8.1 Copy Chapter

• gitlab: upgrade CE to v14.8.1
• gitaly: upgrade to v14.8.1

14.8.0 Copy Chapter

• gitlab: upgrade CE to v14.8.0
• gitaly: upgrade to v14.8.0
• gitlab-pages: upgrade to v1.54.0
• gitlab-shell: v13.23.2

14.7.3 Copy Chapter

• gitlab: upgrade CE to v14.7.3
• gitaly: upgrade to v14.7.3
• golang: upgrade to v1.17.7

14.7.2 Copy Chapter

• gitlab: upgrade CE to v14.7.2
• gitaly: upgrade to v14.7.2
• ubuntu: upgrade to focal-20220113

14.7.1 Copy Chapter

• gitlab: upgrade CE to v14.7.1
• gitaly: upgrade to v14.7.1

14.7.0 Copy Chapter

• gitlab: upgrade CE to v14.7.0
• gitaly: upgrade to v14.7.0
• gitlab-shell: v13.22.2
• gitlab-pages: upgrade to v1.51.0

14.6.3 Copy Chapter

• gitlab: upgrade CE to v14.6.3
• gitaly: upgrade to v14.6.3

14.6.2 Copy Chapter

• gitlab: upgrade CE to v14.6.2
• gitaly: upgrade to v14.6.2
• golang: upgrade to v1.17.6
• ubuntu: upgrade to focal-20220105

14.6.1 Copy Chapter

• gitlab: upgrade CE to v14.6.1
• gitaly: upgrade to v14.6.1

14.6.0 Copy Chapter

• gitlab: upgrade CE to v14.6.0
• gitaly: upgrade to v14.6.0
• gitlab-pages: upgrade to v1.49.0

14.5.2 Copy Chapter

• gitlab: upgrade CE to v14.5.2
• gitaly: upgrade to v14.5.2
• golang: upgrade to v1.17.5

14.5.1 Copy Chapter

• gitlab: upgrade CE to v14.5.1
• gitaly: upgrade to v14.5.1
• gitlab-shell: v13.22.1

14.5.0 Copy Chapter

• gitlab: upgrade CE to v14.5.0
• gitaly: upgrade to v14.5.0
• gitlab-pages: upgrade to v1.48.0
• gitlab-shell: v13.22.0

14.4.4 Copy Chapter

• gitlab: upgrade CE to v14.4.4
• gitaly: upgrade to v14.4.4
• ruby: upgrade to v2.7.5

14.4.3 Copy Chapter

• gitlab: upgrade CE to v14.4.3
• gitaly: upgrade to v14.4.3
• golang: upgrade to v1.17.4

14.4.2 Copy Chapter

• gitlab: upgrade CE to v14.4.2
• gitaly: upgrade to v14.4.2
• redis: upgrade to v6.2.6

14.4.1 Copy Chapter

• gitlab: upgrade CE to v14.4.1
• gitaly: upgrade to v14.4.1

14.4.0 Copy Chapter

• gitlab: upgrade CE to v14.4.0
• gitaly: upgrade to v14.4.0
• gitlab-pages: upgrade to v1.46.0

14.3.3 Copy Chapter

• gitlab: upgrade CE to v14.3.3
• gitaly: upgrade to v14.3.3

14.3.2 Copy Chapter

• gitlab: upgrade CE to v14.3.2
• gitaly: upgrade to v14.3.2
• gitlab-shell: v13.21.1

14.3.1 Copy Chapter

• gitlab: upgrade CE to v14.3.1
• gitaly: upgrade to v14.3.1

14.3.0 Copy Chapter

• gitlab: upgrade CE to v14.3.0
• gitaly: upgrade to v14.3.0
• gitlab-shell: v13.21.0
• gitlab-pages: upgrade to v1.44.0
• ruby: compile ruby from source and use v2.7.4
• ubuntu: upgrade to focal-20211006

14.2.5 Copy Chapter

• gitlab: upgrade CE to v14.2.5
• gitaly: upgrade to v14.2.5

14.2.4 Copy Chapter

• gitlab: upgrade CE to v14.2.4
• gitaly: upgrade to v14.2.4
• golang: upgrade to v1.17.1

14.2.3 Copy Chapter

• gitlab: upgrade CE to v14.2.3
• gitaly: upgrade to v14.2.3

14.2.2 Copy Chapter

• gitlab: upgrade CE to v14.2.2
• gitaly: upgrade to v14.2.2
• ubuntu: upgrade to focal-20210827

14.2.1 Copy Chapter

• gitlab: upgrade CE to v14.2.1
• gitaly: upgrade to v14.2.1

14.2.0 Copy Chapter

• gitlab: upgrade CE to v14.2.0
• gitaly: upgrade to v14.2.0
• gitlab-pages: upgrade to v1.42.0
• golang: upgrade to v1.17

14.1.3 Copy Chapter

• gitlab: upgrade CE to v14.1.3
• gitaly: upgrade to v14.1.3
• golang: upgrade to v1.16.7

14.1.2 Copy Chapter

• gitlab: upgrade CE to v14.1.2
• gitaly: upgrade to v14.1.2
• gitlab-shell: upgrade to v13.19.1

14.1.1 Copy Chapter

• gitlab: upgrade CE to v14.1.1
• gitaly: upgrade to v14.1.1
• ubuntu: upgrade to focal-20210723

14.1.0 Copy Chapter

• gitlab: upgrade CE to v14.1.0
• gitaly: upgrade to v14.1.0

14.0.6 Copy Chapter

• gitlab: upgrade CE to v14.0.6
• gitaly: upgrade to v14.0.6
• golang: upgrade to v1.16.6

14.0.5 Copy Chapter

• gitlab: upgrade CE to v14.0.5
• gitaly: upgrade to v14.0.5

14.0.4 Copy Chapter

• gitlab: upgrade CE to v14.0.4
• gitaly: upgrade to v14.0.4

14.0.3 Copy Chapter

• gitlab: upgrade CE to v14.0.3
• gitaly: upgrade to v14.0.3

14.0.2 Copy Chapter

• gitlab: upgrade CE to v14.0.2
• gitaly: upgrade to v14.0.2

14.0.1 Copy Chapter

• gitlab: upgrade CE to v14.0.1
• gitaly: upgrade to v14.0.1

14.0.0 Copy Chapter

• gitlab: upgrade CE to v14.0.0
• gitaly: upgrade to v14.0.0
• gitlab-shell: upgrade to v13.19.0
• gitlab-pages: upgrade to v1.40.0

13.12.5 Copy Chapter

• gitlab: upgrade CE to v13.12.5
• gitaly: upgrade to v13.12.5
• ubuntu: upgrade to focal-20210609

13.12.4 Copy Chapter

• gitlab: upgrade CE to v13.12.4
• gitaly: upgrade to v13.12.4

13.12.3 Copy Chapter

• gitlab: upgrade CE to v13.12.3
• gitaly: upgrade to v13.12.3
• golang: upgrade to v1.16.5

13.12.2 Copy Chapter

• gitlab: upgrade CE to v13.12.2
• gitaly: upgrade to v13.12.2

13.12.1 Copy Chapter

• gitlab: upgrade CE to v13.12.1
• gitaly: upgrade to v13.12.1

13.12.0 Copy Chapter

• gitlab: upgrade CE to v13.12.0
• gitlab-shell: upgrade to v13.18.0
• gitlab-pages: upgrade to v1.39.0
• gitaly: upgrade to v13.12.0

13.11.4 Copy Chapter

• gitlab: upgrade CE to v13.11.4
• gitaly: upgrade to v13.11.4
• golang: upgrade to v1.16.4
• ubuntu: upgrade to focal-20210416

13.11.3 Copy Chapter

• gitlab: upgrade CE to v13.11.3
• gitaly: upgrade to v13.11.3

13.11.2 Copy Chapter

• gitlab: upgrade CE to v13.11.2
• gitaly: upgrade to v13.11.2

13.11.1 Copy Chapter

• gitlab: upgrade CE to v13.11.1
• gitaly: upgrade to v13.11.1

13.11.0 Copy Chapter

• gitlab: upgrade CE to v13.11.0
• gitaly: upgrade to v13.11.0
• gitlab-pages: upgrade to v1.38.0
• ubuntu: upgrade to focal-20210401

13.10.3 Copy Chapter

• gitlab: upgrade CE to v13.10.3
• gitaly: upgrade to v13.10.3

13.10.2 Copy Chapter

• gitlab: upgrade CE to v13.10.2
• gitaly: upgrade to v13.10.2
• golang: upgrade to v1.16.3
• ubuntu: upgrade to bionic-20210325

13.10.1 Copy Chapter

• gitlab: upgrade CE to v13.10.1
• gitaly: upgrade to v13.10.1
• added libmagic1 to fit requirements of ruby-magic-static-0.3.4 (necessary for puma)

13.10.0 Copy Chapter

• gitlab: upgrade CE to v13.10.0
• gitaly: upgrade to v13.10.0
• gitlab-pages: upgrade to v1.36.0

13.9.5 Copy Chapter

• gitlab: upgrade CE to v13.9.5
• gitaly: upgrade to v13.9.5

13.9.4 Copy Chapter

• gitlab: upgrade CE to v13.9.4
• gitaly: upgrade to v13.9.4
• golang: upgrade to v1.16.2
• ubuntu: upgrade to bionic-20210222

13.9.3 Copy Chapter

• gitlab: upgrade CE to v13.9.3
• gitaly: upgrade to v13.9.3
• gitlab-shell: upgrade to v13.17.0

13.9.2 Copy Chapter

• gitlab: upgrade CE to v13.9.2
• gitaly: upgrade to v13.9.2
• gitlab-workhorse: upgrade to v8.63.2

13.9.1 Copy Chapter

• gitlab: upgrade CE to v13.9.1
• gitaly: upgrade to v13.9.1

13.9.0 Copy Chapter

• gitlab: upgrade CE to v13.9.0
• gitaly: upgrade to v13.9.0
• gitlab-shell: upgrade to v13.16.1
• gitlab-pages: upgrade to v1.35.0
• gitlab-workhorse: upgrade to v8.63.0
• golang: upgrade to v1.16

13.8.4 Copy Chapter

• added SSL_PROTOCOLS option to change protocols of the nginx
• added SSL_REGISTRY_CIPHERS
• added SSL_REGISTRY_PROTOCOLS
• added SSL_PAGES_CIPHERS
• added SSL_PAGES_PROTOCOLS
• gitlab: upgrade CE to v13.8.4
• gitaly: upgrade to v13.8.4
• gitlab-shell: upgrade to v13.15.1

13.8.3 Copy Chapter

• gitlab: upgrade CE to v13.8.3
• gitaly: upgrade to v13.8.3
• golang: upgrade to v1.15.8

13.8.2 Copy Chapter

• gitlab: upgrade CE to v13.8.2
• gitaly: upgrade to v13.8.2

13.8.1 Copy Chapter

• gitlab: upgrade CE to v13.8.1
• gitaly: upgrade to v13.8.1

13.8.0 Copy Chapter

• gitlab: upgrade CE to v13.8.0
• gitaly: upgrade to v13.8.0
• gitlab-shell: upgrade to v13.15.0
• gitlab-workhorse: upgrade to v8.59.0
• gitlab-pages: upgrade to v1.34.0
• golang: upgrade to v1.15.7
• ubuntu: upgrade to bionic-20210118

13.7.4 Copy Chapter

• gitlab: upgrade CE to v13.7.4

13.7.3 Copy Chapter

• gitlab: upgrade CE to v13.7.3
• gitlab-pages: upgrade to v1.34.0
• gitlab-shell: upgrade to v13.7.3
• gitlab-workhorse: upgrade to v8.58.2

13.7.1 Copy Chapter

• gitlab: upgrade CE to v13.7.1
• gitaly: upgrade v13.7.1

13.7.0 Copy Chapter

• gitlab: upgrade CE to v13.7.0
• gitaly: upgrade v13.7.0
• gitlab-shell: upgrade to v13.14.0
• gitlab-pages: upgrade to v1.32.0
• gitlab-workhorse: upgrade to v8.58.0
• ubuntu: upgrade to ubuntu bionic-20201119
• postgresql: upgrade to postgresql 12

13.6.3 Copy Chapter

• gitlab: upgrade CE to v13.6.3
• gitaly: upgrade v13.6.3

13.6.2 Copy Chapter

• gitlab: upgrade CE to v13.6.2
• gitaly: upgrade v13.6.2

13.6.1 Copy Chapter

• gitlab: upgrade CE to v13.6.1
• gitaly: upgrade v13.6.1

13.6.0 Copy Chapter

• gitlab: upgrade CE to v13.6.0
• gitaly: upgrade v13.6.0
• gitlab-shell: upgrade to v13.13.0
• gitlab-pages: upgrade to v1.30.0
• gitlab-workhorse: upgrade to v8.54.0
• use bundler 2.1.4
• use ruby 2.7

13.5.4 Copy Chapter

• gitlab: upgrade CE to v13.5.4
• gitaly: upgrade v13.5.4

13.5.3 Copy Chapter

• gitlab: upgrade CE to v13.5.3
• gitaly: upgrade v13.5.3

13.5.2 Copy Chapter

• gitlab: upgrade CE to v13.5.2
• gitaly: upgrade v13.5.2

13.5.1 Copy Chapter

• gitlab: upgrade CE to v13.5.1
• gitaly: upgrade v13.5.1
• gitlab-shell: upgrade to v13.11.0
• gitlab-pages: upgrade to v1.28.0
• gitlab-workhorse: upgrade to v8.51.0

13.4.4 Copy Chapter

• gitlab: upgrade CE to v13.4.4
• gitaly: upgrade to v13.4.4

13.4.3 Copy Chapter

• gitlab: upgrade CE to v13.4.3
• gitaly: upgrade to v13.4.3

13.4.2 Copy Chapter

• gitlab: upgrade CE to v13.4.2
• gitaly: upgrade to v13.4.2
• gitlab-pages: upgrade to 1.25.0
• gitlab-workhorse: upgrade to 8.46.0
• gitlab-shell: uprade to 13.7.0
• ubuntu: upgrade to bionic-20200921

13.3.4 Copy Chapter

• gitlab: upgrade CE to v13.3.4
• gitaly: upgrade to v13.3.4

13.3.1 Copy Chapter

• gitlab: upgrade CE to v13.3.1
• gitaly: upgrade to v13.3.1

13.3.0 Copy Chapter

• gitlab: upgrade CE to v13.3.0
• gitaly: upgrade to v13.3.0
• gitlab-pages: upgrade to v1.22.0
• gitlab-shell: upgrade to v13.6.0
• gitlab-workhorse: upgrade to v8.39.0

13.2.6 Copy Chapter

• gitlab: upgrade CE to v13.2.6

13.2.4 Copy Chapter

• gitlab: upgrade CE to v13.2.4
• ubuntu: upgrade to bionic-20200713

13.2.3 Copy Chapter

• gitlab: upgrade CE to v13.2.3
• golang: upgrade to 1.14.7
• gitaly: upgrade to 13.2.3
• postgresql: add btree_gist extension

13.2.2 Copy Chapter

• gitlab: upgrade CE to v13.2.2

13.2.1 Copy Chapter

• gitlab: upgrade CE to v13.2.1

13.0.7 Copy Chapter

• gitlab: upgrade CE to v13.0.7

13.0.6 Copy Chapter

• gitlab: upgrade CE to v13.0.6

13.0.5 Copy Chapter

• gitlab: upgrade CE to v13.0.5

13.0.3 Copy Chapter

• gitlab: upgrade CE to v13.0.3

13.0.2 Copy Chapter

• gitlab: upgrade CE to v13.0.2

13.0.1 Copy Chapter

• gitlab: upgrade CE to v13.0.1

13.0.0 Copy Chapter

• gitlab: upgrade CE to v13.0.0

12.10.6 Copy Chapter

• gitlab: upgrade CE to v12.10.6

12.10.4 Copy Chapter

• updated to ubuntu:bionic-20200403
• gitlab-workhorse: update to 8.30.1
• sync: upstream configs
• gitlab: upgrade to 12.10.4

12.9.5 Copy Chapter

• gitlab: updated to 12.9.5
• gitlab-shell: updated to 12.2.0
• gitaly: updated to 12.10.0

12.9.4 Copy Chapter

• gitlab: upgrade CE to v12.9.4
• Update gitlab-workhorse to 8.25.2
• Update golang to 1.13.10

12.9.2 Copy Chapter

• gitlab: upgrade CE to v12.9.2

12.9.1 Copy Chapter

• gitlab: upgrade CE to v12.9.1

12.9.0 Copy Chapter

• gitlab: upgrade CE to v12.9.0
• replaced unicorn with puma
• Removed UNICORN_WORKERS
• Removed UNICORN_TIMEOUT
• Added PUMA_THREADS_MIN
• Added PUMA_THREADS_MAX
• Added PUMA_WORKERS
• Added PUMA_TIMEOUT

12.8.8 Copy Chapter

• gitlab: upgrade CE to v12.8.8

12.8.7 Copy Chapter

• gitlab: upgrade CE to v12.8.7

12.8.6 Copy Chapter

• gitlab: upgrade CE to v12.8.6

12.8.5 Copy Chapter

• gitlab: upgrade CE to v12.8.5

12.8.4 Copy Chapter

• gitlab: upgrade CE to v12.8.4

12.8.3 Copy Chapter

• gitlab: upgrade CE to v12.8.3

12.8.2 Copy Chapter

• gitlab: upgrade CE to v12.8.2

12.8.1 Copy Chapter

• gitlab: upgrade CE to v12.8.1

12.8.0 Copy Chapter

• gitlab: upgrade CE to v12.8.0
• fix: ArgumentError: 'import/{{oauth2_generic_name}}' is not supported #2101

12.7.8 Copy Chapter

• Upgrade GitLab CE to 12.7.8

12.7.7 Copy Chapter

• Upgrade GitLab CE to 12.7.7
• Add Generic OAuth Provider PR#2070

12.7.6 Copy Chapter

• gitlab: upgrade CE to v12.7.6

12.7.5 Copy Chapter

• gitlab: upgrade CE to v12.7.5

12.7.4 Copy Chapter

• Upgrade GitLab CE to 12.7.4
• Update golang to 1.13.7
• Update gitlab-pages to 1.15.0
• Update gitlab-workhorse to 8.20.0
• Update gitaly to 1.85.0

12.7.2 Copy Chapter

• Upgrade GitLab CE to 12.7.2

12.7.0 Copy Chapter

• Update gitlab-shell to 11.0.0
• Upgrade GitLab CE to 12.7.0
• Update golang to 1.13.6
• Update gitaly to 1.83.0
• Update gitlab-pages to 1.14.0
• Update gitlab-workhorse to 8.19.0

12.6.4 Copy Chapter

• gitlab: upgrade CE to v12.6.4

12.6.3 Copy Chapter

• gitlab: upgrade CE to v12.6.3

12.6.2 Copy Chapter

• gitlab: upgrade CE to v12.6.2

12.6.1 Copy Chapter

• gitlab: upgrade CE to v12.6.1

12.6.0 Copy Chapter

• gitlab: upgrade CE to v12.6.0

12.5.7 Copy Chapter

• gitlab: upgrade CE to v12.5.7

12.5.6 Copy Chapter

• gitlab: upgrade CE to v12.5.6

12.5.5 Copy Chapter

• gitlab: upgrade CE to v12.5.5

12.5.4 Copy Chapter

• gitlab: upgrade CE to v12.5.4
• Update golang to 1.12.14

12.5.3 Copy Chapter

• gitlab: upgrade CE to v12.5.3

12.5.2 Copy Chapter

• gitlab: upgrade CE to v12.5.2

12.5.1 Copy Chapter

• gitlab: upgrade CE to v12.5.1

12.5.0 Copy Chapter

• gitlab: upgrade CE to v12.5.0

12.4.3 Copy Chapter

• gitlab: upgrade CE to v12.4.3

12.4.2 Copy Chapter

• gitlab: upgrade CE to v12.4.2

12.4.1 Copy Chapter

• gitlab: upgrade CE to v12.4.1

12.4.0 Copy Chapter

• gitlab: upgrade CE to v12.4.0

12.3.5 Copy Chapter

• gitlab: upgrade CE to v12.3.5

12.3.4 Copy Chapter

• gitlab: upgrade CE to v12.3.4

12.3.3 Copy Chapter

• gitlab: upgrade CE to v12.3.3

12.3.2 Copy Chapter

• gitlab: upgrade CE to v12.3.2

12.3.1 Copy Chapter

• gitlab: upgrade CE to v12.3.1

12.3.0 Copy Chapter

• gitlab: upgrade CE to v12.3.0

12.2.5 Copy Chapter

• gitlab: upgrade CE to v12.2.5

12.2.4 Copy Chapter

• gitlab: upgrade CE to v12.2.4

12.2.3 Copy Chapter

• gitlab: upgrade CE to v12.2.3

12.2.1 Copy Chapter

• gitlab: upgrade CE to v12.2.1

12.2.0 Copy Chapter

• gitlab: upgrade CE to v12.2.0
• upgrade base image to ubuntu:bionic

12.1.6 Copy Chapter

• gitlab: upgrade CE to v12.1.6

12.1.4 Copy Chapter

• gitlab: upgrade CE to v12.1.4

12.1.3 Copy Chapter

• gitlab: upgrade CE to v12.1.3

12.1.2 Copy Chapter

• gitlab: upgrade CE to v12.1.2

12.1.1 Copy Chapter

• gitlab: upgrade CE to v12.1.1

12.1.0 Copy Chapter

• gitlab: upgrade CE to v12.1.0
• Removed MySQL related information and packages. GitLab v12.1.X or greater requires only PostgreSQL. Do an Migration before upgrading to v12.1.X. For more Information have a look at the Migration Guide

12.0.4 Copy Chapter

• gitlab: upgrade CE to v12.0.4

12.0.3 Copy Chapter

• gitlab: upgrade CE to v12.0.3

12.0.2 Copy Chapter

• gitlab: upgrade CE to v12.0.2

12.0.1 Copy Chapter

• gitlab: upgrade CE to v12.0.1

12.0.0 Copy Chapter

• gitlab: upgrade CE to v12.0.0
• Update gitaly to 1.47.0
• Update gitlab-shell to 9.3.0
• Update gitlab-pages to 1.6.1
• ruby: update to 2.6
• python: update to 3

11.11.3 Copy Chapter

• gitlab: upgrade CE to v11.11.3
• Update gitaly to 1.42.4
• Update golang to 1.12.6

11.11.2 Copy Chapter

• gitlab: upgrade CE to v11.11.2
• Update gitaly to 1.42.3

11.11.1 Copy Chapter

• gitlab: upgrade CE to v11.11.1
• Update gitaly to 1.42.2

11.11.0 Copy Chapter

• gitlab: upgrade CE to v11.11.0
• Update gitaly to 1.42.0
• Update gitlab-shell to 9.1.0
• Update gitlab-workhorse to 8.7.0

11.10.4 Copy Chapter

• gitlab: upgrade CE to v11.10.4

11.10.3 Copy Chapter

• gitlab: upgrade CE to v11.10.3

11.10.2 Copy Chapter

• gitlab: upgrade CE to v11.10.2

11.10.1 Copy Chapter

• gitlab: upgrade CE to v11.10.1

11.10.0 Copy Chapter

• gitlab: upgrade CE to v11.10.0

11.9.8 Copy Chapter

• gitlab: upgrade CE to v11.9.8

11.9.7 Copy Chapter

• gitlab: upgrade CE to v11.9.7

11.9.6 Copy Chapter

• gitlab: upgrade CE to v11.9.6

11.9.5 Copy Chapter

• gitlab: upgrade CE to v11.9.5

11.9.4 Copy Chapter

• gitlab: upgrade CE to v11.9.4
• Update gitlab-workhorse to 8.3.3

11.9.1 Copy Chapter

• gitlab: upgrade CE to v11.9.1
• Update gitaly to 1.27.1

11.9.0 Copy Chapter

• gitlab: upgrade CE to v11.9.0

11.8.3 Copy Chapter

• gitlab: upgrade CE to v11.8.3

11.8.2 Copy Chapter

• gitlab: upgrade CE to v11.8.2

11.8.1 Copy Chapter

• gitlab: upgrade CE to v11.8.1

11.8.0 Copy Chapter

• gitlab: upgrade CE to v11.8.0
• Update gitlab-workhorse to 8.3.1
• Update gitaly to 1.20.0
• Update gitlab-pages to 1.5.0

11.7.5 Copy Chapter

• gitlab: upgrade CE to v11.7.5

11.7.4 Copy Chapter

• gitlab: upgrade CE to v11.7.4

11.7.3 Copy Chapter

• gitlab: upgrade CE to v11.7.3
• Update gitlab-workhorse to 8.1.1
• Update gitaly to 1.13.0
• Update gitlab-pages to 1.4.0

11.7.0 Copy Chapter

• gitlab: upgrade CE to v11.7.0

11.6.5 Copy Chapter

• gitlab: upgrade CE to v11.6.5

11.6.4 Copy Chapter

• gitlab: upgrade CE to v11.6.4

11.6.3 Copy Chapter

• gitlab: upgrade CE to v11.6.3

11.6.2 Copy Chapter

• gitlab: upgrade CE to v11.6.2

11.6.1 Copy Chapter

• gitlab: upgrade CE to v11.6.1
• Added GITLAB_IMPERSONATION_ENABLED
• Added OAUTH_SAML_ATTRIBUTE_STATEMENTS_USERNAME
• Added GITLAB_PAGES_ACCESS_CONTROL_SERVER
• Added GITLAB_PAGES_ACCESS_CLIENT_ID
• Added GITLAB_PAGES_ACCESS_CLIENT_SECRET
• Added GITLAB_PAGES_ACCESS_SECRET
• Added GITLAB_PAGES_ACCESS_REDIRECT_URI

11.6.0 Copy Chapter

• gitlab: upgrade CE to v11.6.0
• Update gitaly to 1.7.1
• Update gitlab-shell to 8.4.3
• Update gitlab-workhorse to 7.6.0
• Update golang to 1.11.4
• Added LDAP_USER_ATTRIBUTE_USERNAME
• Added LDAP_USER_ATTRIBUTE_MAIL
• Added LDAP_USER_ATTRIBUTE_NAME
• Added LDAP_USER_ATTRIBUTE_FIRSTNAME
• Added LDAP_USER_ATTRIBUTE_LASTNAME
• Added GITLAB_BACKUP_DIR_CHOWN
• Added GITLAB_BACKUP_DIR_GROUP
• Added GITLAB_PAGES_NGINX_PROXY

11.5.5 Copy Chapter

• gitlab: upgrade CE to v11.5.5

11.5.4 Copy Chapter

• gitlab: upgrade CE to v11.5.4

11.5.3 Copy Chapter

• gitlab: upgrade CE to v11.5.3

11.5.2 Copy Chapter

• gitlab: upgrade CE to v11.5.2

11.5.1-1 Copy Chapter

• Fixed GitLab Dependencies

11.5.1 Copy Chapter

• gitlab: upgrade CE to v11.5.1

11.5.0 Copy Chapter

• gitlab: upgrade CE to v11.5.0

11.4.7 Copy Chapter

• gitlab: upgrade CE to v11.4.7

11.4.6 Copy Chapter

• gitlab: upgrade CE to v11.4.6

11.4.5 Copy Chapter

• gitlab: upgrade CE to v11.4.5

11.4.4 Copy Chapter

• gitlab: upgrade CE to v11.4.4
• golang: update to 1.10.4

11.4.3 Copy Chapter

• gitlab: upgrade CE to v11.4.3

11.4.2 Copy Chapter

• gitlab: upgrade CE to v11.4.2

11.4.1 Copy Chapter

• gitlab: upgrade CE to v11.4.1
• Add docs how to reuse ssh port #1731

11.4.0 Copy Chapter

• gitlab: upgrade CE to v11.4.0
• baseimage: upgrade to xenial-20181005

11.3.6 Copy Chapter

• gitlab: upgrade CE to v11.3.6

11.3.5 Copy Chapter

• gitlab: upgrade CE to v11.3.5

11.3.4 Copy Chapter

• gitlab: upgrade CE to v11.3.4

11.3.3 Copy Chapter

• gitlab: upgrade CE to v11.3.3

11.3.2 Copy Chapter

• gitlab: upgrade CE to v11.3.2

11.3.1 Copy Chapter

• gitlab: upgrade CE to v11.3.1

11.3.0 Copy Chapter

• gitlab: upgrade CE to v11.3.0
• Fix backup config stripping for when AWS & GCS backups are disabled #1725
• Correct Backup Date format for selective backups #1699
• Fix gitlay-ssh symlink to enable rebase/squash in forks

11.2.3 Copy Chapter

• gitlab: upgrade CE to v11.2.3

11.2.2 Copy Chapter

• gitlab: upgrade CE to v11.2.2

11.2.1 Copy Chapter

• gitlab: upgrade CE to v11.2.1

11.2.0 Copy Chapter

• gitlab: upgrade CE to v11.2.0
• ADD GITLAB_DEFAULT_THEME

11.1.4 Copy Chapter

• gitlab: upgrade CE to v11.1.4

11.1.3 Copy Chapter

• gitlab: upgrade CE to v11.1.3
• Upgrade redis to 4.0.9-1

11.1.2 Copy Chapter

• gitlab: upgrade CE to v11.1.2

11.1.1 Copy Chapter

• gitlab: upgrade CE to v11.1.1

11.1.0 Copy Chapter

• gitlab: upgrade CE to v11.1.0

11.0.4 Copy Chapter

• gitlab: upgrade CE to v11.0.4

11.0.3 Copy Chapter

• gitlab: upgrade CE to v11.0.3
• ruby: update to 2.4

11.0.2 Copy Chapter

• gitlab: upgrade CE to v11.0.2

11.0.1 Copy Chapter

• gitlab: upgrade CE to v11.0.1

11.0.0 Copy Chapter

• gitlab: upgrade CE to v11.0.0

10.8.4 Copy Chapter

• gitlab: upgrade CE to v10.8.4

10.8.3-1 Copy Chapter

• Fix boot loops that were introduced during #1621 and will be fixed with #1628

10.8.3 Copy Chapter

• gitlab: upgrade CE to v10.8.3
• Fix potential boot problems on clean setups #1621

10.8.2 Copy Chapter

• gitlab: upgrade CE to v10.8.2

10.8.1 Copy Chapter

• gitlab: upgrade CE to v10.8.1

10.8.0 Copy Chapter

• gitlab: upgrade CE to v10.8.0
• Add support for swarm mode with docker-configs and docker secrets (#1540)

10.7.4 Copy Chapter

• gitlab: upgrade CE to v10.7.4
• FIX GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_ENDPOINT

10.7.3 Copy Chapter

• gitlab: upgrade CE to v10.7.3

10.7.2 Copy Chapter

• gitlab: upgrade CE to v10.7.2

10.7.1 Copy Chapter

• gitlab: upgrade CE to v10.7.1

10.7.0 Copy Chapter

• gitlab: upgrade CE to v10.7.0

• ADD GITLAB_SIDEKIQ_LOG_FORMAT

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_ENABLED

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_REMOTE_DIRECTORY

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_BACKGROUND_UPLOAD

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_PROXY_DOWNLOAD

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_PROVIDER

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_ACCESS_KEY_ID

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_SECRET_ACCESS_KEY

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_REGION

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_HOST

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_ENDPOINT

• ADD GITLAB_ARTIFACTS_OBJECT_STORE_CONNECTION_AWS_PATH_STYLE

• ADD GITLAB_LFS_OBJECT_STORE_ENABLED

• ADD GITLAB_LFS_OBJECT_STORE_REMOTE_DIRECTORY

• ADD GITLAB_LFS_OBJECT_STORE_DIRECT_UPLOAD

• ADD GITLAB_LFS_OBJECT_STORE_BACKGROUND_UPLOAD

• ADD GITLAB_LFS_OBJECT_STORE_PROXY_DOWNLOAD

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_PROVIDER

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_ACCESS_KEY_ID

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_SECRET_ACCESS_KEY

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_REGION

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_HOST

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_ENDPOINT

• ADD GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_PATH_STYLE

• ADD GITLAB_UPLOADS_OBJECT_STORE_ENABLED

• ADD GITLAB_UPLOADS_OBJECT_STORE_REMOTE_DIRECTORY

• ADD GITLAB_UPLOADS_OBJECT_STORE_DIRECT_UPLOAD

• ADD GITLAB_UPLOADS_OBJECT_STORE_BACKGROUND_UPLOAD

• ADD GITLAB_UPLOADS_OBJECT_STORE_PROXY_DOWNLOAD

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_PROVIDER

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_ACCESS_KEY_ID

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_SECRET_ACCESS_KEY

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_REGION

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_HOST

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_ENDPOINT

• ADD GITLAB_UPLOADS_OBJECT_STORE_CONNECTION_AWS_PATH_STYLE

10.6.4 Copy Chapter

• gitlab: upgrade CE to v10.6.4

10.6.3 Copy Chapter

• gitlab: upgrade CE to v10.6.3

10.6.2 Copy Chapter

• gitlab: upgrade CE to v10.6.2
• golang: update to 1.9.5

10.6.1 Copy Chapter

• gitlab: upgrade CE to v10.6.1

10.6.0 Copy Chapter

• gitlab: upgrade CE to v10.6.0

10.5.6 Copy Chapter

• gitlab: security upgrade CE to v10.5.6

10.5.5 Copy Chapter

• gitlab: upgrade CE to v10.5.5

10.5.4 Copy Chapter

• gitlab: upgrade CE to v10.5.4

10.5.3 Copy Chapter

• gitlab: upgrade CE to v10.5.3

10.5.2 Copy Chapter

• gitlab: upgrade CE to v10.5.2
• Fix GITLAB_UPLOADS_STORAGE_PATH

10.5.1 Copy Chapter

• gitlab: upgrade CE to v10.5.1

10.5.0 Copy Chapter

• gitlab: upgrade CE to v10.5.0
• Add GITLAB_UPLOADS_STORAGE_PATH
• Add GITLAB_UPLOADS_BASE_DIR
• Add LDAP_LOWERCASE_USERNAMES

10.4.4 Copy Chapter

• gitlab: upgrade CE to v10.4.4

10.4.3 Copy Chapter

• gitlab: upgrade CE to v10.4.3

10.4.2-1 Copy Chapter

• FIXED SSH Host Key generation through dropping the support for rsa1

10.4.2 Copy Chapter

• gitlab: upgrade CE to v10.4.2

10.4.1 Copy Chapter

• gitlab: upgrade CE to v10.4.1

10.4.0 Copy Chapter

• gitlab: upgrade CE to v10.4.0
• docker: upgrade to ubuntu xenial as baseimage
• golang: update to 1.9.3

10.3.6 Copy Chapter

• gitlab: upgrade CE to v10.3.6

10.3.5 Copy Chapter

• gitlab: upgrade CE to v10.3.5

10.3.4 Copy Chapter

• gitlab: upgrade CE to v10.3.4

10.3.3 Copy Chapter

• gitlab: upgrade CE to v10.3.3
• ADDED AWS_BACKUP_ENCRYPTION 1449
• ADDED AWS_BACKUP_STORAGE_CLASS 1449
• FIXED AWS_BACKUP_MULTIPART_CHUNK_SIZE 1449
• Apply PaX mark to ruby 1458

10.3.2 Copy Chapter

• gitlab: upgrade CE to v10.3.2

10.3.1 Copy Chapter

• gitlab: upgrade CE to v10.3.1

10.3.0 Copy Chapter

• gitlab: upgrade CE to v10.3.0
• REMOVED GITLAB_REPOSITORIES_STORAGES_DEFAULT_FAILURE_COUNT_THRESHOLD
• REMOVED GITLAB_REPOSITORIES_STORAGES_DEFAULT_FAILURE_WAIT_TIME
• REMOVED GITLAB_REPOSITORIES_STORAGES_DEFAULT_FAILURE_RESET_TIME
• REMOVED GITLAB_REPOSITORIES_STORAGES_DEFAULT_STORAGE_TIMEOUT
• REMOVED GITLAB_MAX_OBJECT_SIZE
• REMOVED GITLAB_TIMEOUT

10.2.5 Copy Chapter

• gitlab: upgrade CE to v10.2.5

10.2.4 Copy Chapter

• gitlab: upgrade to CE v10.2.4

10.2.3 Copy Chapter

• gitlab: upgrade to CE v10.2.3

10.2.2 Copy Chapter

• gitlab: upgrade to CE v10.2.2

10.2.1 Copy Chapter

• gitlab: upgrade to CE v10.2.1

10.2.0 Copy Chapter

• gitlab: upgrade to CE v10.2.0

10.1.4 Copy Chapter

• gitlab: upgrade to CE v10.1.4

10.1.3 Copy Chapter

• gitlab: upgrade to CE v10.1.3

10.1.2 Copy Chapter

• gitlab: upgrade to CE v10.1.2

10.1.1 Copy Chapter

• gitlab: upgrade to CE v10.1.1

10.1.0 Copy Chapter

• gitlab: upgrade to CE v10.1.0
• REMOVED `GITALY_ENABLED``
• ADDED GITALY_ARTIFACTS_SERVER
• ADDED GITALY_CLIENT_PATH

10.0.4 Copy Chapter

• gitlab: upgrade to CE v10.0.4

10.0.3 Copy Chapter

• gitlab: upgrade to CE v10.0.3

10.0.2 Copy Chapter

• gitlab: upgrade to CE v10.0.2

10.0.1 Copy Chapter

• gitlab: upgrade to CE v10.0.1

10.0.0 Copy Chapter

• gitlab: upgrade to CE v10.0.0

9.5.5 Copy Chapter

• gitlab: upgrade to CE v9.5.5

9.5.4 Copy Chapter

• gitlab: upgrade to CE v9.5.4

9.5.3 Copy Chapter

• gitlab: upgrade to CE v9.5.3

9.5.2 Copy Chapter

• gitlab: upgrade to CE v9.5.2

9.5.1 Copy Chapter

• gitlab: upgrade to CE v9.5.1

9.5.0 Copy Chapter

• gitlab: upgrade to CE v9.5.0

9.4.5 Copy Chapter

• gitlab: upgrade to CE v9.4.5

9.4.4 Copy Chapter

• gitlab: upgrade to CE v9.4.4

9.4.3 Copy Chapter

• gitlab: upgrade to CE v9.4.3

9.4.2 Copy Chapter

• gitlab: upgrade to CE v9.4.2

9.4.1 Copy Chapter

• gitlab: upgrade to CE v9.4.1

9.4.0-1 Copy Chapter

• Fix asset compiling for missing translations

9.4.0 Copy Chapter

• gitlab: upgrade to CE v9.4.0
• Added support for nginx_real_ip module (#1137)
• Added more security for regenerating certs (#1288)

9.3.9 Copy Chapter

• gitlab: upgrade to CE v9.3.9

9.3.8 Copy Chapter

• gitlab: upgrade to CE v9.3.8
• Added RE2 library to build dependencies (issue 35342)

9.3.7 Copy Chapter

• gitlab: upgrade to CE v9.3.7

9.3.6 Copy Chapter

• gitlab: upgrade to CE v9.3.6

9.3.5 Copy Chapter

• gitlab: upgrade to CE v9.3.5

9.3.4 Copy Chapter

• gitlab: upgrade to CE v9.3.4

9.3.3 Copy Chapter

• gitlab: upgrade to CE v9.3.3

9.3.2 Copy Chapter

• gitlab: upgrade to CE v9.3.2

9.3.1 Copy Chapter

• gitlab: upgrade to CE v9.3.1

9.3.0-1 Copy Chapter

• Add the missing Gitaly config to let git commands over http/https working

9.3.0 Copy Chapter

• gitlab: upgrade to CE v9.3.0
• update baseimage to 14.04.20170608
• Add DB_COLLATION (For MySQL related doesn't recognize by postgres)
• Add GITLAB_PIPELINE_SCHEDULE_WORKER_CRON
• Add GITALY_ENABLED
• Add GITALY_SOCKET_PATH
• Add GITALY_ADDRESS

9.2.7 Copy Chapter

• gitlab: upgrade to CE v9.2.7

9.2.6 Copy Chapter

• gitlab: upgrade to CE v9.2.6

9.2.5 Copy Chapter

• gitlab: upgrade to CE v9.2.5

9.2.2 Copy Chapter

• gitlab: upgrade to CE v9.2.2

9.2.1 Copy Chapter

• gitlab: upgrade to CE v9.2.1

9.2.0 Copy Chapter

• gitlab: upgrade to CE v9.2.0
• Add flexibility to use versions committed into gitlab-ce

9.1.4 Copy Chapter

• gitlab: upgrade to CE v9.1.4

9.1.3 Copy Chapter

• gitlab: upgrade to CE v9.1.3

9.1.2 Copy Chapter

• gitlab: upgrade to CE v9.1.2
• update baseimage to 14.04.20170503

9.1.1 Copy Chapter

• gitlab: upgrade to CE v9.1.1

9.1.0-1 Copy Chapter

• Fix gitlab-workhorse version display

9.1.0 Copy Chapter

• gitlab: upgrade to CE v9.1.0
• gitlab-shell: upgrade to 5.0.2
• gitlab-workhorse: upgrade to 1.4.3

9.0.6 Copy Chapter

• gitlab: upgrade to CE v9.0.6

9.0.5 Copy Chapter

• gitlab: upgrade to CE v9.0.5

9.0.4 Copy Chapter

• gitlab: upgrade to CE v9.0.4

9.0.3 Copy Chapter

• gitlab: upgrade to CE v9.0.3

9.0.2 Copy Chapter

• gitlab: upgrade to CE v9.0.2

9.0.1 Copy Chapter

• gitlab: upgrade to CE v9.0.1
• gitlab-workhorse 1.4.2

9.0.0 Copy Chapter

• gitlab: upgrade to CE v9.0.0
• gitlab-shell 5.0.0
• gitlab-workhorse 1.4.1
• gitlab-pages 0.4.0

8.17.4 Copy Chapter

• gitlab: upgrade to CE v8.17.4

8.17.3 Copy Chapter

• gitlab: upgrade to CE v8.17.3

8.17.2 Copy Chapter

• gitlab: upgrade to CE v8.17.2

8.17.1 Copy Chapter

• gitlab: upgrade to CE v8.17.1
• fixes first problems with gitlab-pages

8.17.0 Copy Chapter

• gitlab: upgrade to CE v8.17.0
• added GITLAB_PAGES_ENABLED
• added GITLAB_PAGES_DOMAIN
• added GITLAB_PAGES_DIR
• added GITLAB_PAGES_PORT
• added GITLAB_PAGES_HTTPS
• added GITLAB_PAGES_EXTERNAL_HTTP
• added GITLAB_PAGES_EXTERNAL_HTTPS
• added SSL_PAGES_KEY_PATH
• added SSL_PAGES_CERT_PATH
• added nodejs 7.x as core dependencies
• added gitlab-pages daemon

8.16.6 Copy Chapter

• gitlab: upgrade to CE v8.16.6
• Fix logical bug of Remote Backup

8.16.5 Copy Chapter

• gitlab: upgrade to CE v8.16.5

8.16.4 Copy Chapter

• gitlab: upgrade to CE v8.16.4

8.16.3 Copy Chapter

• gitlab: upgrade to CE v8.16.3

8.16.2 Copy Chapter

• gitlab: upgrade to CE v8.16.2

8.16.1 Copy Chapter

• gitlab: upgrade to CE v8.16.1

8.16.0 Copy Chapter

• gitlab: upgrade to CE v8.16.0

8.15.4 Copy Chapter

• gitlab: upgrade to CE v8.15.4

8.15.3 Copy Chapter

• gitlab: upgrade to CE v8.15.3

8.15.2 Copy Chapter

• gitlab: upgrade to CE v8.15.2

8.15.1 Copy Chapter

• gitlab: upgrade to CE v8.15.1

8.15.0 Copy Chapter

• gitlab: upgrade to CE v8.15.0
• added GITLAB_MATTERMOST_ENABLED
• added GITLAB_MATTERMOST_URL
• added OAUTH_AUTHENTIQ_CLIENT_ID
• added OAUTH_AUTHENTIQ_CLIENT_SECRET
• added OAUTH_AUTHENTIQ_SCOPE
• added OAUTH_AUTHENTIQ_REDIRECT_URI

8.14.5 Copy Chapter

• gitlab: upgrade to CE v8.14.5

8.14.4 Copy Chapter

• gitlab: upgrade to CE v8.14.4

8.14.3 Copy Chapter

• gitlab: upgrade to CE v8.14.3

8.14.2 Copy Chapter

• gitlab: upgrade to CE v8.14.2

8.14.1 Copy Chapter

• gitlab: upgrade to CE v8.14.1

8.14.0 Copy Chapter

• gitlab: upgrade to CE v8.14.0
• added IMAP_TIMEOUT
• update golang to 1.6.3

8.13.6 Copy Chapter

• gitlab: upgrade to CE v8.13.6

8.13.5 Copy Chapter

• gitlab: upgrade to CE v8.13.5

8.13.4 Copy Chapter

Important: We skipped 8.13.4 because it doesn't contain any changes. For more information 8.13.4 release.

8.13.3 Copy Chapter

• gitlab: upgrade to CE v8.13.3

8.13.2 Copy Chapter

• gitlab: upgrade to CE v8.13.2

8.13.1 Copy Chapter

• gitlab: upgrade to CE v8.13.1

8.13.0 Copy Chapter

• gitlab: upgrade to CE v8.13.0
• added GITLAB_EMAIL_SUBJECT_SUFFIX

8.12.7 Copy Chapter

• gitlab: upgrade to CE v8.12.7

8.12.6 Copy Chapter

• gitlab: upgrade to CE v8.12.6

8.12.5 Copy Chapter

• gitlab: upgrade to CE v8.12.5

8.12.4 Copy Chapter

• gitlab: upgrade to CE v8.12.4

8.12.3 Copy Chapter

• gitlab: upgrade to CE v8.12.3

8.12.2 Copy Chapter

Important: We skipped 8.12.2 because it doesn't contain any changes. For more information 8.12.3 release.

8.12.1 Copy Chapter

• gitlab: upgrade to CE v8.12.1

8.12.0 Copy Chapter

• gitlab: upgrade to CE v8.12.0

8.11.7 Copy Chapter

• gitlab: upgrade to CE v8.11.7

8.11.6 Copy Chapter

• gitlab: upgrade to CE v8.11.6

8.11.5 Copy Chapter

• gitlab: upgrade to CE v8.11.5

8.11.4 Copy Chapter

• gitlab: upgrade to CE v8.11.4

8.11.3 Copy Chapter

• gitlab: upgrade to CE v8.11.3

8.11.2 Copy Chapter

• gitlab: upgrade to CE v8.11.2

8.11.0 Copy Chapter

• gitlab: upgrade to CE v8.11.0
• added GITLAB_SECRETS_SECRET_KEY_BASE
• added GITLAB_SECRETS_OTP_KEY_BASE

Important Copy Chapter

When you start to upgrade from 8.10-7 or below use the key of /home/git/data/.secret for GITLAB_SECRETS_OTP_KEY_BASE otherwise it will break your 2FA .

8.10.7 Copy Chapter

• gitlab: upgrade to CE v8.10.7

8.10.6 Copy Chapter

• gitlab: upgrade to CE v8.10.6

8.10.5 Copy Chapter

• gitlab: upgrade to CE v8.10.5

8.10.4 Copy Chapter

• gitlab: upgrade to CE v8.10.4

8.10.3 Copy Chapter

• gitlab: upgrade to CE v8.10.3

8.10.2-1 Copy Chapter

• Fix OAUTH_GOOGLE_RESTRICT_DOMAIN

8.10.2 Copy Chapter

• gitlab: upgrade to CE v8.10.2
• Improve OAUTH_GOOGLE_RESTRICT_DOMAIN for multiple restricted domains

8.10.1 Copy Chapter

• gitlab: upgrade to CE v8.10.1

8.10.0 Copy Chapter

• gitlab: upgrade to CE v8.10.0

8.9.6 Copy Chapter

• gitlab: upgrade to CE v8.9.6

8.9.5 Copy Chapter

• gitlab: upgrade to CE v8.9.5

8.9.4 Copy Chapter

• gitlab: upgrade to CE v8.9.4

8.9.3 Copy Chapter

• gitlab: upgrade to CE v8.9.3

8.9.2 Copy Chapter

• gitlab: upgrade to CE v8.9.2

8.9.1 Copy Chapter

• gitlab: upgrade to CE v8.9.1

8.9.0 Copy Chapter

• gitlab: upgrade to CE v8.9.0

8.8.5-1 Copy Chapter

• added GitLab Container Registry support
• added SSL_CIPHERS option to change ciphers of the nginx

8.8.5 Copy Chapter

• gitlab: upgrade to CE v8.8.5

8.8.4 Copy Chapter

• gitlab: upgrade to CE v8.8.4
• added GITLAB_PROJECTS_LIMIT configuration option

8.8.3 Copy Chapter

• gitlab: upgrade to CE v8.8.3

8.8.2 Copy Chapter

• gitlab: upgrade to CE v8.8.2

8.8.1 Copy Chapter

• gitlab: upgrade to CE v8.8.1

8.8.0 Copy Chapter

• gitlab: upgrade to CE v8.8.0
• oauth: exposed OAUTH_GITHUB_URL and OAUTH_GITHUB_VERIFY_SSL options for users for GitHub Enterprise.

8.7.6 Copy Chapter

• gitlab: upgrade to CE v8.7.6

8.7.5 Copy Chapter

• gitlab: upgrade to CE v8.7.5

8.7.3 Copy Chapter

• gitlab: upgrade to CE v8.7.3

8.7.2 Copy Chapter

• gitlab: upgrade to CE v8.7.2

8.7.1 Copy Chapter

• gitlab: upgrade to CE v8.7.1

8.7.0 Copy Chapter

• gitlab-shell: upgrade to v.2.7.2
• gitlab: upgrade to CE v8.7.0
• SSO: OAUTH_ALLOW_SSO now specifies a comma separated list of providers.
• OAuth: Added OAUTH_EXTERNAL_PROVIDERS to specify external oauth providers.
• Exposed GITLAB_TRUSTED_PROXIES configuration parameter

8.6.7 Copy Chapter

• added GITLAB_SIGNUP_ENABLED option to enable/disable signups
• gitlab: upgrade to CE v8.6.7

8.6.6 Copy Chapter

• gitlab: upgrade to CE v8.6.6

8.6.5 Copy Chapter

• gitlab: upgrade to CE v8.6.5

8.6.4 Copy Chapter

• gitlab: upgrade to CE v8.6.4

8.6.3 Copy Chapter

• gitlab-shell: upgrade to v.2.6.12
• gitlab: upgrade to CE v8.6.3

8.6.2 Copy Chapter

• gitlab: upgrade to CE v8.6.2

8.6.1 Copy Chapter

• gitlab: upgrade to CE v8.6.1

8.6.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.11
• gitlab-workhorse: upgrade to v0.7.1
• gitlab: upgrade to CE v8.6.0
• exposed configuration parameters for auth0 OAUTH support
• fixed relative_url support

8.5.8 Copy Chapter

• gitlab: upgrade to CE v8.5.8

8.5.7 Copy Chapter

• gitlab: upgrade to CE v8.5.7

8.5.5 Copy Chapter

• gitlab: upgrade to CE v8.5.5

8.5.4 Copy Chapter

• gitlab: upgrade to CE v8.5.4

8.5.3 Copy Chapter

• gitlab: upgrade to CE v8.5.3

8.5.1 Copy Chapter

• gitlab: upgrade to CE v8.5.1

8.5.0 Copy Chapter

• gitlab-workhorse: upgrade to v0.6.4
• gitlab: upgrade to CE v8.5.0
• firstrun: expose GITLAB_ROOT_EMAIL configuration option
• expose OAUTH_AUTO_LINK_SAML_USER configuration parameter

8.4.4 Copy Chapter

• gitlab: upgrade to CE v8.4.4

8.4.3 Copy Chapter

• gitlab: upgrade to CE v8.4.3

8.4.2 Copy Chapter

• gitlab-workhorse: upgrade to v0.6.2
• gitlab: upgrade to CE v8.4.2

8.4.1 Copy Chapter

• gitlab: upgrade to CE v8.4.1

8.4.0-1 Copy Chapter

• assets:precompile moved back to build time

8.4.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.10
• gitlab-workhorse: upgrade to v0.6.1
• gitlab: upgrade to CE v8.4.0
• oauth: expose cas3 oauth configuration options
• oauth: expose azure oauth configuration options
• assets:precompile executed at runtime

8.3.4 Copy Chapter

• gitlab-workhorse: upgrade to v0.5.4
• gitlab: upgrade to CE v8.3.4
• expose LDAP_TIMEOUT configuration parameter

8.3.2 Copy Chapter

• gitlab: upgrade to CE v8.3.2

8.3.1 Copy Chapter

• gitlab: upgrade to CE v8.3.1

8.3.0-1 Copy Chapter

• fixed static asset routing when GITLAB_RELATIVE_URL_ROOT is used.

8.3.0 Copy Chapter

• envsubst is now used for updating the configurations
• renamed config CA_CERTIFICATES_PATH to SSL_CA_CERTIFICATES_PATH
• renamed config GITLAB_HTTPS_HSTS_ENABLED to NGINX_HSTS_ENABLED
• renamed config GITLAB_HTTPS_HSTS_MAXAGE to NGINX_HSTS_MAXAGE
• renamed config GITLAB_BACKUPS to GITLAB_BACKUP_SCHEDULE
• gitlab-workhorse: upgrade to v0.5.1
• gitlab: upgrade to CE v8.3.0
• expose GITLAB_MAX_OBJECT_SIZE configuration parameter
• removed NGINX_MAX_UPLOAD_SIZE configuration parameter
• gitlab-shell: upgrade to v.2.6.9

8.2.3 Copy Chapter

• fixed static asset routing when GITLAB_RELATIVE_URL_ROOT is used.
• added GITLAB_BACKUP_PG_SCHEMA configuration parameter
• gitlab: upgrade to CE v8.2.3

8.2.2 Copy Chapter

• added GITLAB_DOWNLOADS_DIR configuration parameter
• DB_TYPE parameter renamed to DB_ADAPTER with mysql2 and postgresql as accepted values
• exposed DB_ENCODING parameter
• gitlab: upgrade to CE v8.2.2

8.2.1-1 Copy Chapter

• fixed typo while setting the value of GITLAB_ARTIFACTS_DIR

8.2.1 Copy Chapter

• expose rack_attack configuration options
• gitlab-shell: upgrade to v.2.6.8
• gitlab: upgrade to CE v8.2.1
• added GITLAB_ARTIFACTS_ENABLED configuration parameter
• added GITLAB_ARTIFACTS_DIR configuration parameter

8.2.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.7
• gitlab-workhorse: upgrade to v.0.4.2
• gitlab: upgrade to CE v8.2.0
• added GITLAB_SHARED_DIR configuration parameter
• added GITLAB_LFS_OBJECTS_DIR configuration parameter
• added GITLAB_PROJECTS_BUILDS configuration parameter
• added GITLAB_LFS_ENABLED configuration parameter

8.1.4 Copy Chapter

• gitlab: upgrade to CE v8.1.4

8.1.3 Copy Chapter

• proper long-term fix for http/https cloning when GITLAB_RELATIVE_URL_ROOT is used
• gitlab: upgrade to CE v8.1.3
• Expose Facebook OAUTH configuration parameters

8.1.2 Copy Chapter

• gitlab: upgrade to CE v8.1.2
• removed GITLAB_SATELLITES_TIMEOUT configuration parameter

8.1.0-2 Copy Chapter

• Recompile assets when GITLAB_RELATIVE_URL_ROOT is used Fixes #481

8.1.0-1 Copy Chapter

• temporary fix for http/https cloning when GITLAB_RELATIVE_URL_ROOT is used

8.1.0 Copy Chapter

• gitlab: upgrade to CE v8.1.0
• gitlab-git-http-server: upgrade to v0.3.0

8.0.5-1 Copy Chapter

• speed up container startup by compiling assets at image build time
• test connection to redis-server

8.0.5 Copy Chapter

• gitlab: upgrade to CE v.8.0.5

8.0.4-2 Copy Chapter

• fix http/https cloning when GITLAB_RELATIVE_URL_ROOT is used
• allow user to override OAUTH_ENABLED setting

8.0.4-1 Copy Chapter

• update baseimage to sameersbn/ubuntu:14.04.20151011

8.0.4 Copy Chapter

• gitlab: upgrade to CE v.8.0.4

8.0.3 Copy Chapter

• gitlab: upgrade to CE v.8.0.3

8.0.2 Copy Chapter

• gitlab: upgrade to CE v.8.0.2
• added IMAP_STARTTLS parameter, defaults to false
• expose oauth parameters for crowd server

8.0.0 Copy Chapter

• set default value of DB_TYPE to postgres
• added sample Kubernetes rc and service description files
• expose GITLAB_BACKUP_ARCHIVE_PERMISSIONS parameter
• gitlab: upgrade to CE v.8.0.0
• added GITLAB_SECRETS_DB_KEY_BASE parameter
• added GITLAB_NOTIFY_ON_BROKEN_BUILDS and GITLAB_NOTIFY_PUSHER parameters
• added options to email IMAP and reply by email feature
• set value of GITLAB_EMAIL to SMTP_USER if defined, else default to [email protected]
• removed GITLAB_ROBOTS_OVERRIDE parameter. Override default robots.txt if GITLAB_ROBOTS_PATH exists.
• added CI redirection using GITLAB_CI_HOST parameter

7.14.3 Copy Chapter

• gitlab: upgrade to CE v.7.14.3

7.14.2 Copy Chapter

• Apply grsecurity policies to nodejs binary #394
• Fix broken emojis post migration #196
• gitlab-shell: upgrade to v.2.6.5
• gitlab: upgrade to CE v.7.14.2

7.14.1 Copy Chapter

• gitlab: upgrade to CE v.7.14.1

7.14.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.4
• gitlab: upgrade to CE v.7.14.0

7.13.5 Copy Chapter

• gitlab: upgrade to CE v.7.13.5

7.13.4 Copy Chapter

• gitlab: upgrade to CE v.7.13.4

7.13.3 Copy Chapter

• gitlab: upgrade to CE v.7.13.3

7.13.2 Copy Chapter

• gitlab: upgrade to CE v.7.13.2

7.13.1 Copy Chapter

• gitlab: upgrade to CE v.7.13.1

7.13.0 Copy Chapter

• expose SAML OAuth provider configuration
• expose OAUTH_AUTO_SIGN_IN_WITH_PROVIDER configuration
• gitlab: upgrade to CE v.7.13.0

7.12.2-2 Copy Chapter

• enable persistence .secret file used in 2FA

7.12.2-1 Copy Chapter

• fixed gitlab:backup:restore raketask

7.12.2 Copy Chapter

• gitlab: upgrade to CE v.7.12.2

7.12.1 Copy Chapter

• gitlab: upgrade to CE v.7.12.1

7.12.0 Copy Chapter

• added SMTP_TLS configuration parameter
• gitlab: upgrade to CE v.7.12.0
• added OAUTH_AUTO_LINK_LDAP_USER configuration parameter

7.11.4-1 Copy Chapter

• base image update to fix SSL vulnerability

7.11.4 Copy Chapter

• gitlab: upgrade to CE v.7.11.4

7.11.3 Copy Chapter

• gitlab: upgrade to CE v.7.11.3

7.11.2 Copy Chapter

• gitlab: upgrade to CE v.7.11.2

7.11.0 Copy Chapter

• init: added SIDEKIQ_MEMORY_KILLER_MAX_RSS configuration option
• init: added SIDEKIQ_SHUTDOWN_TIMEOUT configuration option
• gitlab-shell: upgrade to v.2.6.3
• gitlab: upgrade to CE v.7.11.0
• init: removed GITLAB_PROJECTS_VISIBILITY ENV parameter

7.10.4 Copy Chapter

• gitlab: upgrade to CE v.7.10.4

7.10.3 Copy Chapter

• gitlab: upgrade to CE v.7.10.3

7.10.2 Copy Chapter

• init: added support for remote AWS backups
• gitlab: upgrade to CE v.7.10.2

7.10.1 Copy Chapter

• gitlab: upgrade to CE v.7.10.1

7.10.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.2
• gitlab: upgrade to CE v.7.10.0
• init: removed ENV variables to configure External Issue Tracker integration
• init: added GITLAB_EMAIL_REPLY_TO configuration option
• init: added LDAP_BLOCK_AUTO_CREATED_USERS configuration option

7.9.4 Copy Chapter

• gitlab: upgrade to CE v.7.9.4

7.9.3 Copy Chapter

• added NGINX_PROXY_BUFFERING option
• added NGINX_ACCEL_BUFFERING option
• added GITLAB_GRAVATAR_ENABLED option
• added GITLAB_GRAVATAR_HTTP_URL option
• added GITLAB_GRAVATAR_HTTPS_URL option
• fixes: "transfer closed with xxx bytes remaining to read" error
• gitlab: upgrade to CE v.7.9.3

7.9.2 Copy Chapter

• gitlab: upgrade to CE v.7.9.2

7.9.1 Copy Chapter

• init: set default value of SMTP_OPENSSL_VERIFY_MODE to none
• gitlab: upgrade to CE v.7.9.1

7.9.0 Copy Chapter

• gitlab-shell: upgrade to v.2.6.0
• gitlab: upgrade to CE v.7.9.0
• init: set default value of UNICORN_WORKERS to 3
• init: set default value of SMTP_OPENSSL_VERIFY_MODE to peer
• init: removed GITLAB_RESTRICTED_VISIBILITY configuration option, can be set from the UI
• init: added BitBucket OAuth configuration support
• init: added GITLAB_EMAIL_DISPLAY_NAME configuration option

7.8.4 Copy Chapter

• gitlab: upgrade to CE v.7.8.4

7.8.2 Copy Chapter

• gitlab: upgrade to CE v.7.8.2

7.8.1 Copy Chapter

• gitlab-shell: upgrade to v.2.5.4
• gitlab: upgrade to CE v.7.8.1

7.8.0 Copy Chapter

• update postgresql client to the latest version, Closes #249
• removed GITLAB_SIGNUP configuration option, can be set from gitlab ui
• removed GITLAB_SIGNIN configuration option, can be set from gitlab ui
• removed GITLAB_PROJECTS_LIMIT configuration option, can be set from gitlab ui
• removed GITLAB_GRAVATAR_ENABLED configuration option, can be set from gitlab ui
• gitlab-shell: upgrade to v.2.5.3
• gitlab: upgrade to CE v.7.8.0
• init: set LDAP_PORT default value to 389
• init: set LDAP_METHOD default value to plain
• init: added gitlab oauth configuration support

7.7.2 Copy Chapter

• gitlab-shell: upgrade to v.2.4.2
• gitlab: upgrade to CE v.7.7.2

7.7.1 Copy Chapter

• gitlab: upgrade to CE v.7.7.1

7.7.0 Copy Chapter

• init: added GOOGLE_ANALYTICS_ID configuration option
• added support for mantis issue tracker
• fixed log rotation configuration
• gitlab-shell: upgrade to v.2.4.1
• gitlab: upgrade to CE v.7.7.0

7.6.2 Copy Chapter

• gitlab: upgrade to CE v.7.6.2

7.6.1 Copy Chapter

• disable nginx ipv6 if host does not support it.
• init: added GITLAB_BACKUP_TIME configuration option
• gitlab: upgrade to CE v.7.6.1

7.6.0 Copy Chapter

• add support for configuring piwik
• gitlab-shell: upgrade to v.2.4.0
• gitlab: upgrade to CE v.7.6.0

7.5.3 Copy Chapter

• accept BACKUP parameter while running the restore rake task, closes #220
• init: do not run gitlab:satellites:create rake task at startup
• gitlab: upgrade to CE v.7.5.3

7.5.2 Copy Chapter

• gitlab: upgrade to CE v.7.5.2

7.5.1 Copy Chapter

• gitlab: upgrade to CE v.7.5.1
• gitlab-shell to v2.2.0
• added GITLAB_TIMEZONE configuration option
• added GITLAB_EMAIL_ENABLED configuration option

7.4.4 Copy Chapter

• gitlab: upgrade to CE v.7.4.4
• added SSL_VERIFY_CLIENT configuration option
• added NGINX_WORKERS configuration option
• added USERMAP_UID and USERMAP_GID configuration option

7.4.3 Copy Chapter

• gitlab: upgrade to CE v.7.4.3

7.4.2 Copy Chapter

• gitlab: upgrade to CE v.7.4.2

7.4.0 Copy Chapter

• gitlab: upgrade to CE v.7.4.0
• config: added LDAP_ACTIVE_DIRECTORY configuration option
• added SMTP_OPENSSL_VERIFY_MODE configuration option
• feature: gitlab logs volume
• automatically compile assets if relative_url is changed
• launch all daemons via supervisord

7.3.2-1 Copy Chapter

• fix mysql status check

7.3.2 Copy Chapter

• upgrade to gitlab-ce 7.3.2
• removed internal mysql server
• added support for fetching DB_NAME, DB_USER and DB_PASS from the postgresql linkage
• added support for fetching DB_NAME, DB_USER and DB_PASS from the mysql linkage
• gitlab-shell: upgrade to v.2.0.1
• added GITLAB_GRAVATAR_ENABLED configuration option
• added fig.yml

7.3.1-3 Copy Chapter

• fix mysql command again!

7.3.1-2 Copy Chapter

• fix mysql server status check

7.3.1-1 Copy Chapter

• plug bash vulnerability by switching to dash shell
• automatically run the gitlab:setup rake task for new installs

7.3.1 Copy Chapter

• upgrade to gitlab-ce 7.3.1

7.3.0 Copy Chapter

• upgrade to gitlab-ce 7.3.0
• added GITLAB_WEBHOOK_TIMEOUT configuration option
• upgrade to gitlab-shell 2.0.0
• removed internal redis server
• shutdown the container gracefully

7.2.2 Copy Chapter

• upgrade to gitlab-ce 7.2.2
• added GITLAB_HTTPS_HSTS_ENABLED configuration option (advanced config)
• added GITLAB_HTTPS_HSTS_MAXAGE configuration option (advanced config)
• upgrade to gitlab-shell 1.9.8
• purge development packages after install. shaves off ~300MB from the image.
• rebase image on sameersbn/debian:jessie.20140918 base image
• added GITLAB_SSH_HOST configuration option
• added GITLAB_USERNAME_CHANGE configuration option

7.2.1-1 Copy Chapter

• removed the GITLAB_HTTPS_ONLY configuration option
• added NGINX_X_FORWARDED_PROTO configuration option
• optimization: talk directly to the unicorn worker from gitlab-shell

7.2.1 Copy Chapter

• upgrade to gitlab-ce 7.2.1
• added new SMTP_ENABLED configuration option.

7.2.0-1 Copy Chapter

• fix nginx static route handling when GITLAB_RELATIVE_URL_ROOT is used.
• fix relative root access without the trailing '/' character
• added separate server block for http config in gitlab.https.permissive. Fixes #127
• added OAUTH_GOOGLE_RESTRICT_DOMAIN config option.

7.2.0 Copy Chapter

• upgrade to gitlab-ce 7.2.0
• update to the sameersbn/ubuntu:14.04.20140818 baseimage
• remove /var/lib/apt/lists to optimize image size.
• disable UsePrivilegeSeparation in sshd configuration, fixes #122
• added OAUTH_BLOCK_AUTO_CREATED_USERS configuration option
• added OAUTH_ALLOW_SSO configuration option
• added github oauth configuration support
• added twitter oauth configuration support
• added google oauth configuration support
• added support for jira issue tracker
• added support for redmine issue tracker
• update to gitlab-shell 1.9.7
• update to the sameersbn/ubuntu:14.04.20140812 baseimage

7.1.1 Copy Chapter

• removed "add_header X-Frame-Options DENY" setting from the nginx config. fixes #110
• upgrade to gitlab-ce 7.1.1
• run /etc/init.d/gitlab as git user, plays nicely with selinux

7.1.0 Copy Chapter

• removed GITLAB_SUPPORT configuration option
• upgrade to gitlab-ce 7.1.0
• clone gitlab-ce and gitlab-shell sources from the git repo.
• disable pam authentication module in sshd
• update to the sameersbn/ubuntu:14.04.20140628 baseimage
• no more root access over ssh, use nsenter instead
• upgrade to nginx-1.6.x series from the nginx/stable ppa

7.0.0 Copy Chapter

• upgrade to gitlab-7.0.0
• fix repository and gitlab-satellites directory permissions.
• added GITLAB_RESTRICTED_VISIBILITY configuration option
• fix backup restore operation
• upgrade to gitlab-shell 1.9.6
• added app:sanitize command
• automatically migrate database when gitlab version is updated
• upgrade to gitlab-shell 1.9.5

6.9.2 Copy Chapter

• upgrade to gitlab-ce 6.9.2

6.9.1 Copy Chapter

• upgrade to gitlab-ce 6.9.1

6.9.0 Copy Chapter

• upgrade to gitlab-ce 6.9.0
• added GITLAB_RELATIVE_URL_ROOT configuration option
• added NGINX_MAX_UPLOAD_SIZE configuration to specify the maximum acceptable size of attachments.

6.8.2 Copy Chapter

• upgrade to gitlab-ce 6.8.2
• renamed configuration option GITLAB_SHELL_SSH_PORT to GITLAB_SSH_PORT
• added GITLAB_PROJECTS_VISIBILITY configuration option to specify the default project visibility level.
• generate and store ssh host keys at the data store.
• default GITLAB_PROJECTS_LIMIT is now set to 100
• use sameersbn/ubuntu:14.04.20140508 base image, the trusted build of sameersbn/ubuntu:14.04.20140505 seems to be broken
• use sameersbn/ubuntu:14.04.20140505 base image
• added CA_CERTIFICATES_PATH configuration option to specify trusted root certificates.
• added SSL support
• added SSL_DHPARAM_PATH configuration option to specify path of dhparam.pem file.
• added SSL_KEY_PATH configuration option to specify path of ssl key.
• added SSL_CERTIFICATE_PATH configuration option to specify path of ssl certificate
• added GITLAB_HTTPS_ONLY configuration option to configure strict https only access
• added SSL_SELF_SIGNED configuration option to specify use of self signed ssl certificates.
• fix git over ssh when the default http/https ports are not used.
• compile the assets only if it does not exist or if the gitlab version has changed.
• upgrade gitlab-shell to version 1.9.4
• cache compiled assets to boost application startup.
• fix symlink to uploads directory

6.8.1 Copy Chapter

• upgrade to gitlab-ce 6.8.1

6.8.0 Copy Chapter

• upgrade to gitlab-shell 1.9.3
• added GITLAB_SIGNIN setting to enable or disable standard login form
• upgraded to gitlab-ce version 6.8.0
• added support for linking with redis container.
• use sameersbn/ubuntu as the base docker image
• install postgresql-client to fix restoring backups when used with a postgresql database backend.

6.7.5 Copy Chapter

• upgrade gitlab to 6.7.5
• support linking to mysql and postgresql containers
• added DEFAULT_PROJECTS_LIMIT configuration option

6.7.4 Copy Chapter

• upgrade gitlab to 6.7.4
• added SMTP_AUTHENTICATION configuration option, defaults to :login.
• added LDAP configuration options.

6.7.3 Copy Chapter

• upgrade gitlab to 6.7.3
• install ruby2.0 from ppa

6.7.2 Copy Chapter

• upgrade gitlab to 6.7.2
• upgrade gitlab-shell to 1.9.1
• reorganize repo
• do not perform system upgrades (http://crosbymichael.com/dockerfile-best-practices-take-2.html)

6.6.5 Copy Chapter

• upgraded to gitlab-6.6.5

v6.6.4 Copy Chapter

• upgraded to gitlab-6.6.4
• added changelog
• removed postfix mail delivery
• added SMTP_DOMAIN configuration option
• added SMTP_STARTTLS configuration option
• added SMTP_DOMAIN configuration option
• added DB_PORT configuration option
• changed backup time to 4am (UTC)

v6.6.2 Copy Chapter

• upgraded to gitlab-6.6.2
• added automated daily/monthly backups feature
• documented ssh login details for maintenance tasks.
• perform upgrade of git, nginx and other system packages
• added GITLAB_SHELL_SSH_PORT configuration option
• added app:rake command for executing gitlab rake tasks
• documented hardware requirements

v6.6.1 Copy Chapter

• upgraded to gitlabhq-6.6.1
• reformatted README

CONTRIBUTING Copy Section

GitLab-CI Configuration

When using your own GitLab instance, the provided .gitlab-ci.yml will automatically be using the settings provided by the GitLab instance. If needed, several options can be overriden.

Overrides for these values can be set within the project, under Settings -> CI/CD -> Variables.

README Copy Section

sameersbn/gitlab:19.2.2

• Introduction
  • Changelog
• Contributing
• Team
• Issues
• Announcements
• Prerequisites
• Installation
• Quick Start
• Configuration
  • Data Store
  • Database
    • PostgreSQL (Recommended)
      • External PostgreSQL Server
      • Linking to PostgreSQL Container
      • Upgrading PostgreSQL
  • Redis
    • Internal Redis Server
    • External Redis Server
    • Linking to Redis Container
  • Mail
    • Microsoft Graph Mailer
    • Reply by email
  • SSL
    • Generation of a Self Signed Certificate
    • Strengthening the server security
    • Installation of the SSL Certificates
    • Enabling HTTPS support
    • Configuring HSTS
    • Using HTTPS with a load balancer
    • Establishing trust with your server
    • Installing Trusted SSL Server Certificates
  • Deploy to a subdirectory (relative url root)
  • OmniAuth Integration
    • CAS3
    • Authentiq
    • Google
    • Twitter
    • GitHub
    • GitLab
    • BitBucket
    • SAML
    • Crowd
    • Microsoft Azure
    • Generic OAuth2
    • OpenID Connect
    • JWT
  • Gitlab Pages
  • External Issue Trackers
  • Host UID / GID Mapping
  • Piwik
  • Feature flags
  • Exposing ssh port in dockerized gitlab-ce
  • Available Configuration Parameters
• Maintenance
  • Creating Backups
  • Restoring Backups
  • Automated Backups
  • Amazon Web Services (AWS) Remote Backups
  • Google Cloud Storage (GCS) Remote Backups
  • Rake Tasks
  • Import Repositories
  • Upgrading
  • Shell Access
• Monitoring
  • Health Check
• Container Registry
• Deploy in Docker Swarm mode, with HTTPS handled by Traefik proxy and Docker Registry
• References

Introduction Copy Chapter

Dockerfile to build a GitLab image for the Docker open source container platform.

GitLab CE is set up in the Docker image using the install from source method as documented in the official GitLab documentation.

For other methods to install GitLab please refer to the Official GitLab Installation Guide which includes a GitLab image for Docker.

Contributing Copy Chapter

If you find this image useful here's how you can help:

• Send a Pull Request with your awesome new features and bug fixes
• Be a part of the community and help resolve Issues
• Support the development of this image with a donation

Team Copy Chapter

• Niclas Mietz (solidnerd)
• Sameer Naik (sameersbn)

See Contributors for the complete list developers that have contributed to this project.

Issues Copy Chapter

Docker is actively being developed and tested by a thriving community of developers and testers and every release of Docker features many enhancements and bugfixes.

Given the nature of the development and release cycle it is very important that you have the latest version of Docker installed because any issue that you encounter might have already been fixed with a newer Docker release.

Install the most recent version of the Docker Engine for your platform using the official Docker releases, which can also be installed using:

wget -qO- https://get.docker.com/ | sh

Fedora and RHEL/CentOS users should try disabling selinux with setenforce 0 and check if resolves the issue. If it does than there is not much that I can help you with. You can either stick with selinux disabled (not recommended by redhat) or switch to using ubuntu.

You may also set DEBUG=true to enable debugging of the entrypoint script, which could help you pinpoint any configuration issues.

If using the latest docker version and/or disabling selinux does not fix the issue then please file an issue request on the issues page.

In your issue report please make sure you provide the following information:

• The host distribution and release version.
• Output of the docker version command
• Output of the docker info command
• The docker run command you used to run the image (mask out the sensitive bits).

Prerequisites Copy Chapter

Your docker host needs to have 1GB or more of available RAM to run GitLab. Please refer to the GitLab hardware requirements documentation for additional information.

Installation Copy Chapter

Automated builds of the image are available on Dockerhub and is the recommended method of installation.

docker pull sameersbn/gitlab:19.2.2

You can also pull the latest tag which is built from the repository HEAD

docker pull sameersbn/gitlab:latest

Alternatively you can build the image locally.

docker build -t sameersbn/gitlab github.com/sameersbn/docker-gitlab

Quick Start Copy Chapter

The quickest way to get started is using docker-compose.

wget https://raw.githubusercontent.com/sameersbn/docker-gitlab/master/docker-compose.yml

Generate random strings that are at least 64 characters long for each of GITLAB_SECRETS_OTP_KEY_BASE, GITLAB_SECRETS_DB_KEY_BASE, GITLAB_SECRETS_SECRET_KEY_BASE, GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE. These values are used for the following:

• GITLAB_SECRETS_OTP_KEY_BASE is used to encrypt 2FA secrets in the database. If you lose or rotate this secret, none of your users will be able to log in using 2FA.
• GITLAB_SECRETS_DB_KEY_BASE is used to encrypt CI secret variables, as well as import credentials, in the database. If you lose or rotate this secret, you will not be able to use existing CI secrets.
• GITLAB_SECRETS_SECRET_KEY_BASE is used for password reset links, and other 'standard' auth features. If you lose or rotate this secret, password reset tokens in emails will reset.
• GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE is used for reading settings from encrypted files such as SMTP or LDAP credentials.

Tip: You can generate a random string using pwgen -Bsv1 64 and assign it as the value of GITLAB_SECRETS_DB_KEY_BASE.

Also generate random strings that are typically 32 characters long for each of:

• GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
• GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY
• GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT

These values are used for ActiveRecord::Encryption encrypted columns. Details can be found under Active Record Encryption.

Start GitLab using:

docker-compose up

Alternatively, you can manually launch the gitlab container and the supporting postgresql and redis containers by following this three step guide.

Step 1. Launch a postgresql container

docker run --name gitlab-postgresql -d \
    --env 'DB_NAME=gitlabhq_production' \
    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \
    --env 'DB_EXTENSION=pg_trgm,btree_gist' \
    --volume /srv/docker/gitlab/postgresql:/var/lib/postgresql \
    kkimurak/sameersbn-postgresql:17

Step 2. Launch a redis container

docker run --name gitlab-redis -d \
    --volume /srv/docker/gitlab/redis:/data \
    redis:7

Step 3. Launch the gitlab container

docker run --name gitlab -d \
    --link gitlab-postgresql:postgresql --link gitlab-redis:redisio \
    --publish 10022:22 --publish 10080:80 \
    --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' \
    --env 'GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alpha-numeric-string' \
    --env 'GITLAB_SECRETS_SECRET_KEY_BASE=long-and-random-alpha-numeric-string' \
    --env 'GITLAB_SECRETS_OTP_KEY_BASE=long-and-random-alpha-numeric-string' \
    --env 'GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE=long-and-random-alpha-numeric-string' \
    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY=["long-and-random-alpha-numeric-string"]' \
    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY=["long-and-random-alpha-numeric-string"]' \
    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT=long-and-random-alpha-numeric-string' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Please refer to Available Configuration Parameters to understand GITLAB_PORT and other configuration options

NOTE: Please allow a couple of minutes for the GitLab application to start.

Point your browser to http://localhost:10080 and set a password for the root user account.

You should now have the GitLab application up and ready for testing. If you want to use this image in production then please read on.

The rest of the document will use the docker command line. You can quite simply adapt your configuration into a docker-compose.yml file if you wish to do so.

Configuration Copy Chapter

Data Store Copy Section

GitLab is a code hosting software and as such you don't want to lose your code when the docker container is stopped/deleted. To avoid losing any data, you should mount a volume at,

• /home/git/data

Note: that if you are using the docker-compose approach, you must "inspect" the volumes (docker volume inspect) to check the mounted path.

SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.

mkdir -p /srv/docker/gitlab/gitlab
sudo chcon -Rt svirt_sandbox_file_t /srv/docker/gitlab/gitlab

Volumes can be mounted in docker by specifying the -v option in the docker run command.

docker run --name gitlab -d \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Database Copy Section

GitLab uses a database backend to store its data. You can configure this image to use PostgreSQL.

Note: GitLab requires PostgreSQL now. So use an older image < 12.1 or migrate to PostgresSQL

PostgreSQL

Important note: This image is shipped with different versions of the postgresql-client.

During the startup of the container, the major version of the database system is checked based on the specified connection destination. Only the version of the postgresql-client, that matches the major version of the Postgres database is used. If the major version of any version of the included clients does not match, the latest client is used (but may cause issues). All other versions of the postgresql-client are deleted at runtime.

This behavior can be checked using the command docker logs and an output like the following should be available:

…
Configuring gitlab::database
- Installing postgresql client to avoid version mismatch on dumping
-- Detected server version: 160009
- Generating /home/git/.postgresqlrc
16 postgresql:5432 gitlabhq_production
- Uninstalling unused client(s): postgresql-client-13 postgresql-client-14 postgresql-client-15 postgresql-client-17
…

Please note furthermore, that only compatible versions of the postgresql-client to GitLab are shipped with this image. Currently, these belong to

• postgresql-client-17 and
• postgresql-client-18 (not officially supported).

Notes:

• GitLab CE version 13.7.0 and later requires PostgreSQL version 12.x.
• GitLab CE version 16.0.0 and later requires PostgreSQL version 13.x.
• GitLab CE version 17.0.0 and later requires PostgreSQL version 14.x.
• GitLab CE version 18.0.0 and later requires PostgreSQL version 16.x.
• GitLab CE version 19.1.0 and later requires PostgreSQL version 17.x.

External PostgreSQL Server

The image also supports using an external PostgreSQL Server. This is also controlled via environment variables.

CREATE ROLE gitlab with LOGIN CREATEDB PASSWORD 'password';
CREATE DATABASE gitlabhq_production;
GRANT ALL PRIVILEGES ON DATABASE gitlabhq_production to gitlab;

Additionally, since GitLab 8.6.0 the pg_trgm extension should also be loaded for the gitlabhq_production database.

We are now ready to start the GitLab application.

Note: The following applies assuming that the PostgreSQL server host is 192.168.1.100.

docker run --name gitlab -d \
    --env 'DB_HOST=192.168.1.100' \
    --env 'DB_NAME=gitlabhq_production' \
    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Linking to PostgreSQL Container

You can link this image with a postgresql container for the database requirements. The alias of the postgresql server container should be set to postgresql while linking with the gitlab image.

If a postgresql container is linked, only the DB_HOST and DB_PORT settings are automatically retrieved using the linkage. You may still need to set other database connection parameters such as the DB_NAME, DB_USER, DB_PASS and so on.

To illustrate linking with a postgresql container, we will use the sameersbn/postgresql image. When using postgresql image in production you should mount a volume for the postgresql data store. Please refer the README of docker-postgresql for details.

First, let's pull the postgresql image from the docker index.

docker pull kkimurak/sameersbn-postgresql:17

For data persistence lets create a store for the postgresql and start the container.

SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.

mkdir -p /srv/docker/gitlab/postgresql
sudo chcon -Rt svirt_sandbox_file_t /srv/docker/gitlab/postgresql

The run command looks like this.

docker run --name gitlab-postgresql -d \
    --env 'DB_NAME=gitlabhq_production' \
    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \
    --env 'DB_EXTENSION=pg_trgm' \
    --volume /srv/docker/gitlab/postgresql:/var/lib/postgresql \
    kkimurak/sameersbn-postgresql:17

The above command will create a database named gitlabhq_production and also create a user named gitlab with the password password with access to the gitlabhq_production database.

We are now ready to start the GitLab application.

docker run --name gitlab -d --link gitlab-postgresql:postgresql \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Here the image will also automatically fetch the DB_NAME, DB_USER and DB_PASS variables from the postgresql container as they are specified in the docker run command for the postgresql container. This is made possible using the magic of docker links and works with the following images:

• postgres,
• kkimurak/sameersbn-postgresql, or
• sameersbn/postgresql .

Upgrading PostgreSQL

When this Gitlab image upgrades its dependency on specific version of PostgreSQL you will need to make sure to use corresponding version of PostgreSQL.

If you are setting a brand new install, there is no data migration involved. However, if you already have an existing setup, the PostgreSQL data will need to be migrated as you are upgrading the version of PostgreSQL.

If you are using PostgreSQL image other than sameersbn/postgresql you will need make sure that the image you are using can handle migration itself, or, you will need to migrate the data yourself before starting newer version of PostgreSQL.

Following project provides Docker image that handles migration of PostgreSQL data: tianon/postgres-upgrade

After migration of the data, verify that other PostgreSQL configuration files in its data folder are copied over as well. One such file is pg_hba.conf, it will need to be copied from old version data folder into new version data folder.

Redis Copy Section

GitLab uses the redis server for its key-value data store. The redis server connection details can be specified using environment variables.

Internal Redis Server

The internal redis server has been removed from the image. Please use a linked redis container or specify a external redis connection.

External Redis Server

The image can be configured to use an external redis server. The configuration should be specified using environment variables while starting the GitLab image.

Note: The following applies assuming that the redis server host is 192.168.1.100.

docker run --name gitlab -it --rm \
    --env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \
    sameersbn/gitlab:19.2.2

Linking to Redis Container

You can link this image with a redis container to satisfy gitlab's redis requirement. The alias of the redis server container should be set to redisio while linking with the gitlab image.

To illustrate linking with a redis container, we will use the redis image. Please refer the README for details.

First, let's pull the redis image from the docker index.

docker pull redis:7

Lets start the redis container

docker run --name gitlab-redis -d \
    --volume /srv/docker/gitlab/redis:/data \
    redis:7

We are now ready to start the GitLab application.

docker run --name gitlab -d --link gitlab-redis:redisio \
    sameersbn/gitlab:19.2.2

Mail

The mail configuration should be specified using environment variables while starting the GitLab image. The configuration defaults to using gmail to send emails and requires the specification of a valid username and password to login to the gmail servers.

If you are using Gmail then all you need to do is:

docker run --name gitlab -d \
    --env '[email protected]' --env 'SMTP_PASS=PASSWORD' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Please refer the Available Configuration Parameters section for the list of SMTP parameters that can be specified.

Microsoft Graph Mailer

As Microsoft is retiring basic authentication for SMTP AUTH on Exchange Online, mail delivery via SMTP using a Microsoft 365 mailbox is no longer viable for many tenants. The image supports GitLab's native Microsoft Graph Mailer, which sends emails via the Microsoft Graph API using OAuth 2.0 client credentials.

To enable it, register an application in Azure AD, grant it the Mail.Send Application permission (not Delegated), and have an administrator consent to it. Then start the container with:

docker run --name gitlab -d \
    --env 'MICROSOFT_GRAPH_MAILER_ENABLED=true' \
    --env 'MICROSOFT_GRAPH_MAILER_USER_ID=00000000-0000-0000-0000-000000000000' \
    --env 'MICROSOFT_GRAPH_MAILER_TENANT=contoso.onmicrosoft.com' \
    --env 'MICROSOFT_GRAPH_MAILER_CLIENT_ID=11111111-1111-1111-1111-111111111111' \
    --env 'MICROSOFT_GRAPH_MAILER_CLIENT_SECRET=YOUR_CLIENT_SECRET' \
    --env '[email protected]' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:18.11.0

MICROSOFT_GRAPH_MAILER_USER_ID is the Object ID of the Microsoft 365 user whose mailbox will be used, and GITLAB_EMAIL must be that user's primary email address. SMTP_ENABLED should stay at its default (false) when Graph Mailer is used. Please refer the Available Configuration Parameters section for the list of Microsoft Graph Mailer parameters that can be specified.

Reply by email

Since version 8.0.0 GitLab adds support for commenting on issues by replying to emails.

To enable this feature you need to provide IMAP configuration parameters that will allow GitLab to connect to your mail server and read mails. Additionally, you may need to specify GITLAB_INCOMING_EMAIL_ADDRESS if your incoming email address is not the same as the IMAP_USER.

If your email provider supports email sub-addressing then you should add the +%{key} placeholder after the user part of the email address, eg. GITLAB_INCOMING_EMAIL_ADDRESS=reply+%{key}@example.com. Please read the documentation on reply by email to understand the requirements for this feature.

If you are using Gmail then all you need to do is:

docker run --name gitlab -d \
    --env '[email protected]' --env 'IMAP_PASS=PASSWORD' \
    --env 'GITLAB_INCOMING_EMAIL_ADDRESS=USER+%{key}@gmail.com' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Please refer the Available Configuration Parameters section for the list of IMAP parameters that can be specified.

SSL

Access to the gitlab application can be secured using SSL so as to prevent unauthorized access to the data in your repositories. While a CA certified SSL certificate allows for verification of trust via the CA, a self-signed certificate can also provide an equal level of trust verification as long as each client takes some additional steps to verify the identity of your website. I will provide instructions on achieving this towards the end of this section.

Jump to the Using HTTPS with a load balancer section if you are using a load balancer such as hipache, haproxy or nginx.

To secure your application via SSL you basically need two things:

• Private key (.key)
• SSL certificate (.crt)

When using CA certified certificates, these files are provided to you by the CA. When using self-signed certificates you need to generate these files yourself. Skip to Strengthening the server security section if you are armed with CA certified SSL certificates.

Generation of a Self Signed Certificate

Generation of a self-signed SSL certificate involves a simple 3-step procedure:

STEP 1: Create the server private key

openssl genrsa -out gitlab.key 2048

STEP 2: Create the certificate signing request (CSR)

openssl req -new -key gitlab.key -out gitlab.csr

STEP 3: Sign the certificate using the private key and CSR

openssl x509 -req -days 3650 -in gitlab.csr -signkey gitlab.key -out gitlab.crt

Congratulations! You now have a self-signed SSL certificate valid for 10 years.

Strengthening the server security

This section provides you with instructions to strengthen your server security. To achieve this we need to generate stronger DHE parameters.

openssl dhparam -out dhparam.pem 2048

Installation of the SSL Certificates

Out of the four files generated above, we need to install the gitlab.key, gitlab.crt and dhparam.pem files at the gitlab server. The CSR file is not needed, but do make sure you safely backup the file (in case you ever need it again).

The default path that the gitlab application is configured to look for the SSL certificates is at /home/git/data/certs, this can however be changed using the SSL_KEY_PATH, SSL_CERTIFICATE_PATH and SSL_DHPARAM_PATH configuration options.

If you remember from above, the /home/git/data path is the path of the data store, which means that we have to create a folder named certs/ inside the volume to where /home/git/data point and copy the files into it and as a measure of security we'll update the permission on the gitlab.key file to only be readable by the owner.

In case use of docker-compose ...

$>docker volume inspect

Look for "< user >_gitlab-data" and copy the "certs" directory into the "Mountpoint"

mkdir -p /srv/docker/gitlab/gitlab/certs
cp gitlab.key /srv/docker/gitlab/gitlab/certs/
cp gitlab.crt /srv/docker/gitlab/gitlab/certs/
cp dhparam.pem /srv/docker/gitlab/gitlab/certs/
chmod 400 /srv/docker/gitlab/gitlab/certs/gitlab.key

Great! We are now just one step away from having our application secured.

Enabling HTTPS support

HTTPS support can be enabled by setting the GITLAB_HTTPS option to true. Additionally, when using self-signed SSL certificates you need to the set SSL_SELF_SIGNED option to true as well. Assuming we are using self-signed certificates

docker run --name gitlab -d \
    --publish 10022:22 --publish 10080:80 --publish 10443:443 \
    --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=10443' \
    --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer.

Configuring HSTS

HSTS if supported by the browsers makes sure that your users will only reach your sever via HTTPS. When the user comes for the first time it sees a header from the server which states for how long from now this site should only be reachable via HTTPS - that's the HSTS max-age value.

With NGINX_HSTS_MAXAGE you can configure that value. The default value is 31536000 seconds. If you want to disable an already sent HSTS MAXAGE value, set it to 0.

docker run --name gitlab -d \
 --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
 --env 'NGINX_HSTS_MAXAGE=2592000' \
 --volume /srv/docker/gitlab/gitlab:/home/git/data \
 sameersbn/gitlab:19.2.2

If you want to completely disable HSTS set NGINX_HSTS_ENABLED to false.

Using HTTPS with a load balancer

Load balancers like nginx/haproxy/hipache talk to backend applications over plain http and as such the installation of ssl keys and certificates are not required and should NOT be installed in the container. The SSL configuration has to instead be done at the load balancer.

However, when using a load balancer you MUST set GITLAB_HTTPS to true. Additionally, you will need to set the SSL_SELF_SIGNED option to true if self-signed SSL certificates are in use.

With this in place, you should configure the load balancer to support handling of https requests. But that is out of the scope of this document. Please refer to Using SSL/HTTPS with HAProxy for information on the subject.

When using a load balancer, you probably want to make sure the load balancer performs the automatic http to https redirection. Information on this can also be found in the link above.

In summation, when using a load balancer, the docker command would look for the most part something like this:

docker run --name gitlab -d \
    --publish 10022:22 --publish 10080:80 \
    --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=443' \
    --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

Again, drop the --env 'SSL_SELF_SIGNED=true' option if you are using CA certified SSL certificates.

In case GitLab responds to any kind of POST request (login, OAUTH, changing settings etc.) with a 422 HTTP Error, consider adding this to your reverse proxy configuration:

proxy_set_header X-Forwarded-Ssl on; (nginx format)

Establishing trust with your server

This section deals will self-signed ssl certificates. If you are using CA certified certificates, you're done.

This section is more of a client side configuration so as to add a level of confidence at the client to be 100 percent sure they are communicating with whom they think they.

This is simply done by adding the servers certificate into their list of trusted certificates. On ubuntu, this is done by copying the gitlab.crt file to /usr/local/share/ca-certificates/ and executing update-ca-certificates.

Again, this is a client side configuration which means that everyone who is going to communicate with the server should perform this configuration on their machine. In short, distribute the gitlab.crt file among your developers and ask them to add it to their list of trusted ssl certificates. Failure to do so will result in errors that look like this:

git clone https://git.local.host/gitlab-foss.git
fatal: unable to access 'https://git.local.host/gitlab-foss.git': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

You can do the same at the web browser. Instructions for installing the root certificate for firefox can be found here. You will find similar options chrome, just make sure you install the certificate under the authorities tab of the certificate manager dialog.

There you have it, that's all there is to it.

Installing Trusted SSL Server Certificates

If your GitLab CI server is using self-signed SSL certificates then you should make sure the GitLab CI server certificate is trusted on the GitLab server for them to be able to talk to each other.

The default path image is configured to look for the trusted SSL certificates is at /home/git/data/certs/ca.crt, this can however be changed using the SSL_CA_CERTIFICATES_PATH configuration option.

Copy the ca.crt file into the certs directory on the datastore. The ca.crt file should contain the root certificates of all the servers you want to trust. With respect to GitLab CI, this will be the contents of the gitlab_ci.crt file as described in the README of the docker-gitlab-ci container.

By default, our own server certificate gitlab.crt is added to the trusted certificates list.

Deploy to a subdirectory (relative url root)

By default, GitLab expects that your application is running at the root (e.g.. /). This section explains how to run your application inside a directory.

Let's assume we want to deploy our application to '/git'. GitLab needs to know this directory to generate the appropriate routes. This can be specified using the GITLAB_RELATIVE_URL_ROOT configuration option like so:

docker run --name gitlab -it --rm \
    --env 'GITLAB_RELATIVE_URL_ROOT=/git' \
    --volume /srv/docker/gitlab/gitlab:/home/git/data \
    sameersbn/gitlab:19.2.2

GitLab will now be accessible at the /git path, e.g. http://www.example.com/git.

Note: The GITLAB_RELATIVE_URL_ROOT parameter should always begin with a slash and SHOULD NOT have any trailing slashes.

OmniAuth Integration

GitLab leverages OmniAuth to allow users to sign in using Twitter, GitHub, and other popular services. Configuring OmniAuth does not prevent standard GitLab authentication or LDAP (if configured) from continuing to work. Users can choose to sign in using any of the configured mechanisms.

Refer to the GitLab documentation for additional information.

CAS3

To enable the CAS OmniAuth provider you must register your application with your CAS instance. This requires the service URL GitLab will supply to CAS. It should be something like: https://git.example.com:443/users/auth/cas3/callback?url. By default handling for SLO is enabled, you only need to configure CAS for backchannel logout.

For example, if your cas server url is https://sso.example.com, then adding --env 'OAUTH_CAS3_SERVER=https://sso.example.com' to the docker run command enables support for CAS3 OAuth. Please refer to Available Configuration Parameters for additional CAS3 configuration parameters.

Authentiq

To enable the Authentiq OmniAuth provider for passwordless authentication you must register an application with Authentiq. Please refer to the GitLab documentation for the procedure to generate the client ID and secret key with Authentiq.

Once you have the API client id and client secret generated, configure them using the OAUTH_AUTHENTIQ_CLIENT_ID and OAUTH_AUTHENTIQ_CLIENT_SECRET environment variables respectively.

For example, if your API key is xxx and the API secret key is yyy, then adding --env 'OAUTH_AUTHENTIQ_CLIENT_ID=xxx' --env 'OAUTH_AUTHENTIQ_CLIENT_SECRET=yyy' to the docker run command enables support for Authentiq OAuth.

You may want to specify OAUTH_AUTHENTIQ_REDIRECT_URI as well. The OAuth scope can be altered as well with OAUTH_AUTHENTIQ_SCOPE (defaults to 'aq:name email~rs address aq:push').

Google

To enable the Google OAuth2 OmniAuth provider you must register your application with Google. Google will generate a client ID and secret key for you to use. Please refer to the GitLab documentation for the procedure to generate the client ID and secret key with google.

Once you have the client ID and secret keys generated, configure them using the OAUTH_GOOGLE_API_KEY and OAUTH_GOOGLE_APP_SECRET environment variables respectively.

For example, if your client ID is xxx.apps.googleusercontent.com and client secret key is yyy, then adding --env 'OAUTH_GOOGLE_API_KEY=xxx.apps.googleusercontent.com' --env 'OAUTH_GOOGLE_APP_SECRET=yyy' to the docker run command enables support for Google OAuth.

You can also restrict logins to a single domain by adding --env "OAUTH_GOOGLE_RESTRICT_DOMAIN='example.com'".

Facebook

To enable the Facebook OAuth2 OmniAuth provider you must register your application with Facebook. Facebook will generate an API key and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the API key and secret.

Once you have the API key and secret generated, configure them using the OAUTH_FACEBOOK_API_KEY and OAUTH_FACEBOOK_APP_SECRET environment variables respectively.

For example, if your API key is xxx and the API secret key is yyy, then adding --env 'OAUTH_FACEBOOK_API_KEY=xxx' --env 'OAUTH_FACEBOOK_APP_SECRET=yyy' to the docker run command enables support for Facebook OAuth.

Twitter

To enable the Twitter OAuth2 OmniAuth provider you must register your application with Twitter. Twitter will generate an API key and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the API key and secret with twitter.

Once you have the API key and secret generated, configure them using the OAUTH_TWITTER_API_KEY and OAUTH_TWITTER_APP_SECRET environment variables respectively.

For example, if your API key is xxx and the API secret key is yyy, then adding --env 'OAUTH_TWITTER_API_KEY=xxx' --env 'OAUTH_TWITTER_APP_SECRET=yyy' to the docker run command enables support for Twitter OAuth.

GitHub

To enable the GitHub OAuth2 OmniAuth provider you must register your application with GitHub. GitHub will generate a Client ID and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the Client ID and secret with github.

Once you have the Client ID and secret generated, configure them using the OAUTH_GITHUB_API_KEY and OAUTH_GITHUB_APP_SECRET environment variables respectively.

For example, if your Client ID is xxx and the Client secret is yyy, then adding --env 'OAUTH_GITHUB_API_KEY=xxx' --env 'OAUTH_GITHUB_APP_SECRET=yyy' to the docker run command enables support for GitHub OAuth.

Users of GitHub Enterprise may want to specify OAUTH_GITHUB_URL and OAUTH_GITHUB_VERIFY_SSL as well.

GitLab

To enable the GitLab OAuth2 OmniAuth provider you must register your application with GitLab. GitLab will generate a Client ID and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the Client ID and secret with GitLab.

Once you have the Client ID and secret generated, configure them using the OAUTH_GITLAB_API_KEY and OAUTH_GITLAB_APP_SECRET environment variables respectively.

For example, if your Client ID is xxx and the Client secret is yyy, then adding --env 'OAUTH_GITLAB_API_KEY=xxx' --env 'OAUTH_GITLAB_APP_SECRET=yyy' to the docker run command enables support for GitLab OAuth.

BitBucket

To enable the BitBucket OAuth2 OmniAuth provider you must register your application with BitBucket. BitBucket will generate a Client ID and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the Client ID and secret with BitBucket.

Once you have the Client ID and secret generated, configure them using the OAUTH_BITBUCKET_API_KEY and OAUTH_BITBUCKET_APP_SECRET environment variables respectively.

For example, if your Client ID is xxx and the Client secret is yyy, then adding --env 'OAUTH_BITBUCKET_API_KEY=xxx' --env 'OAUTH_BITBUCKET_APP_SECRET=yyy' to the docker run command enables support for BitBucket OAuth.

SAML

GitLab can be configured to act as a SAML 2.0 Service Provider (SP). This allows GitLab to consume assertions from a SAML 2.0 Identity Provider (IdP) such as Microsoft ADFS to authenticate users. Please refer to the GitLab documentation.

The following parameters have to be configured to enable SAML OAuth support in this image: OAUTH_SAML_ASSERTION_CONSUMER_SERVICE_URL, OAUTH_SAML_IDP_CERT_FINGERPRINT, OAUTH_SAML_IDP_SSO_TARGET_URL, OAUTH_SAML_ISSUER and OAUTH_SAML_NAME_IDENTIFIER_FORMAT.

You can also override the default "Sign in with" button label with OAUTH_SAML_LABEL.

Please refer to Available Configuration Parameters for the default configurations of these parameters.

Crowd

To enable the Crowd server OAuth2 OmniAuth provider you must register your application with Crowd server.

Configure GitLab to enable access the Crowd server by specifying the OAUTH_CROWD_SERVER_URL, OAUTH_CROWD_APP_NAME and OAUTH_CROWD_APP_PASSWORD environment variables.

Auth0

To enable the Auth0 OmniAuth provider you must register your application with auth0.

Configure the following environment variables OAUTH_AUTH0_CLIENT_ID, OAUTH_AUTH0_CLIENT_SECRET and OAUTH_AUTH0_DOMAIN to complete the integration.

Microsoft Azure

To enable the Microsoft Azure OAuth2 OmniAuth provider you must register your application with Azure. Azure will generate a Client ID, Client secret and Tenant ID for you to use. Please refer to the GitLab documentation for the procedure.

Once you have the Client ID, Client secret and Tenant ID generated, configure them using the OAUTH_AZURE_API_KEY, OAUTH_AZURE_API_SECRET and OAUTH_AZURE_TENANT_ID environment variables respectively.

For example, if your Client ID is xxx, the Client secret is yyy and the Tenant ID is zzz, then adding --env 'OAUTH_AZURE_API_KEY=xxx' --env 'OAUTH_AZURE_API_SECRET=yyy' --env 'OAUTH_AZURE_TENANT_ID=zzz' to the docker run command enables support for Microsoft Azure OAuth.

Also you can configure v2 endpoint (azure_activedirectory_v2) by using OAUTH_AZURE_ACTIVEDIRECTORY_V2_CLIENT_ID, OAUTH_AZURE_ACTIVEDIRECTORY_V2_CLIENT_SECRET and OAUTH_AZURE_ACTIVEDIRECTORY_V2_TENANT_ID environment variables. Optionally you can change label of login button using the OAUTH_AZURE_ACTIVEDIRECTORY_V2_LABEL.

Generic OAuth2

To enable the Generic OAuth2 provider, you must register your application with your provider. You also need to confirm OAuth2 provider app's ID and secret, the client options and the user's response structure.

As an example this code has been tested with Keycloak, with the following variables: OAUTH2_GENERIC_APP_ID, OAUTH2_GENERIC_APP_SECRET, OAUTH2_GENERIC_CLIENT_SITE, OAUTH2_GENERIC_CLIENT_USER_INFO_URL, OAUTH2_GENERIC_CLIENT_AUTHORIZE_URL, OAUTH2_GENERIC_CLIENT_TOKEN_URL, OAUTH2_GENERIC_CLIENT_END_SESSION_ENDPOINT, OAUTH2_GENERIC_ID_PATH, OAUTH2_GENERIC_USER_UID, OAUTH2_GENERIC_USER_NAME, OAUTH2_GENERIC_USER_EMAIL, OAUTH2_GENERIC_AUTHORIZE_PARAMS_SCOPE, OAUTH2_GENERIC_LABEL and OAUTH2_GENERIC_NAME.

See GitLab documentation and Omniauth-oauth2-generic documentation for more details.

OpenID Connect

To enable OpenID Connect provider, you must register your application with your provider. You also need to confirm OpenID Connect provider app's ID and secret, the client options and the user's response structure.

To use OIDC set at least OAUTH_OIDC_ISSUER and OAUTH_OIDC_CLIENT_ID.

See GitLab OIDC documentation and OmniAuth OpenID Connect documentation.

JWT

To enable the JWT OmniAuth provider, you must register your application with JWT. JWT provides you with a secret key for you to use.

To use JWT set at least OAUTH_JWT_SECRET and OAUTH_JWT_AUTH_URL.