[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-10005":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":35,"trendingCount":16,"starSnapshotCount":16,"syncStatus":19,"lastSyncTime":36,"discoverSource":37},10005,"docker-gitlab","sameersbn\u002Fdocker-gitlab","sameersbn","Dockerized GitLab","http:\u002F\u002Fwww.damagehead.com\u002Fdocker-gitlab\u002F",null,"Shell",8091,2142,277,557,0,4,7,2,40.99,"MIT License",false,"master",true,[26,27,28,29,30,31,32],"code-hosting","containers","docker","docker-image","git","gitlab","gitlab-ce","2026-06-12 02:02:15","# sameersbn\u002Fgitlab:18.11.2\n\n[![CircleCI](https:\u002F\u002Fcircleci.com\u002Fgh\u002Fsameersbn\u002Fdocker-gitlab\u002Ftree\u002Fmaster.svg?style=svg)](https:\u002F\u002Fcircleci.com\u002Fgh\u002Fsameersbn\u002Fdocker-gitlab\u002Ftree\u002Fmaster)\n\n- [Introduction](#introduction)\n    - [Changelog](Changelog.md)\n- [Contributing](#contributing)\n- [Team](#team)\n- [Issues](#issues)\n- [Announcements](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-gitlab\u002Fissues\u002F39)\n- [Prerequisites](#prerequisites)\n- [Installation](#installation)\n- [Quick Start](#quick-start)\n- [Configuration](#configuration)\n    - [Data Store](#data-store)\n    - [Database](#database)\n        - [PostgreSQL (Recommended)](#postgresql)\n            - [External PostgreSQL Server](#external-postgresql-server)\n            - [Linking to PostgreSQL Container](#linking-to-postgresql-container)\n            - [Upgrading PostgreSQL](#upgrading-postgresql)\n    - [Redis](#redis)\n        - [Internal Redis Server](#internal-redis-server)\n        - [External Redis Server](#external-redis-server)\n        - [Linking to Redis Container](#linking-to-redis-container)\n    - [Mail](#mail)\n        - [Microsoft Graph Mailer](#microsoft-graph-mailer)\n        - [Reply by email](#reply-by-email)\n    - [SSL](#ssl)\n        - [Generation of a Self Signed Certificate](#generation-of-a-self-signed-certificate)\n        - [Strengthening the server security](#strengthening-the-server-security)\n        - [Installation of the SSL Certificates](#installation-of-the-ssl-certificates)\n        - [Enabling HTTPS support](#enabling-https-support)\n        - [Configuring HSTS](#configuring-hsts)\n        - [Using HTTPS with a load balancer](#using-https-with-a-load-balancer)\n        - [Establishing trust with your server](#establishing-trust-with-your-server)\n        - [Installing Trusted SSL Server Certificates](#installing-trusted-ssl-server-certificates)\n    - [Deploy to a subdirectory (relative url root)](#deploy-to-a-subdirectory-relative-url-root)\n    - [OmniAuth Integration](#omniauth-integration)\n        - [CAS3](#cas3)\n        - [Authentiq](#authentiq)\n        - [Google](#google)\n        - [Twitter](#twitter)\n        - [GitHub](#github)\n        - [GitLab](#gitlab)\n        - [BitBucket](#bitbucket)\n        - [SAML](#saml)\n        - [Crowd](#crowd)\n        - [Microsoft Azure](#microsoft-azure)\n        - [Generic OAuth2](#generic-oauth2)\n        - [OpenID Connect](#openid-connect)\n        - [JWT](#jwt)\n    - [Gitlab Pages](#gitlab-pages)\n    - [External Issue Trackers](#external-issue-trackers)\n    - [Host UID \u002F GID Mapping](#host-uid--gid-mapping)\n    - [Piwik](#piwik)\n    - [Feature flags](#feature-flags)\n    - [Exposing ssh port in dockerized gitlab-ce](docs\u002Fexposing-ssh-port.md)\n    - [Available Configuration Parameters](#available-configuration-parameters)\n- [Maintenance](#maintenance)\n    - [Creating Backups](#creating-backups)\n    - [Restoring Backups](#restoring-backups)\n    - [Automated Backups](#automated-backups)\n    - [Amazon Web Services (AWS) Remote Backups](#amazon-web-services-aws-remote-backups)\n    - [Google Cloud Storage (GCS) Remote Backups](#google-cloud-storage-gcs-remote-backups)\n    - [Rake Tasks](#rake-tasks)\n    - [Import Repositories](#import-repositories)\n    - [Upgrading](#upgrading)\n    - [Shell Access](#shell-access)\n- [Monitoring](#monitoring)\n    - [Health Check](#health-check)\n- [Container Registry](docs\u002Fcontainer_registry.md)\n- [Deploy in Docker Swarm mode, with HTTPS handled by Traefik proxy and Docker Registry](docs\u002Fdocker-swarm-traefik-registry.md)\n- [References](#references)\n\n## Introduction\n\nDockerfile to build a [GitLab](https:\u002F\u002Fabout.gitlab.com\u002F) image for the [Docker](https:\u002F\u002Fwww.docker.com\u002Fproducts\u002Fdocker-engine) open source container platform.\n\nGitLab CE is set up in the Docker image using the [install from source](https:\u002F\u002Fdocs.gitlab.com\u002Fce\u002Finstall\u002Finstallation.html) method as documented in the official GitLab documentation.\n\nFor other methods to install GitLab please refer to the [Official GitLab Installation Guide](https:\u002F\u002Fabout.gitlab.com\u002Finstall\u002F) which includes a [GitLab image for Docker](https:\u002F\u002Fdocs.gitlab.com\u002Fomnibus\u002Fdocker\u002F).\n\n## Contributing\n\nIf you find this image useful here's how you can help:\n\n- Send a Pull Request with your awesome new features and bug fixes\n- Be a part of the community and help resolve [Issues](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-gitlab\u002Fissues)\n- Support the development of this image with a [donation](http:\u002F\u002Fwww.damagehead.com\u002Fdonate\u002F)\n\n## Team\n\n- Niclas Mietz ([solidnerd](https:\u002F\u002Fgithub.com\u002Fsolidnerd))\n- Sameer Naik ([sameersbn](https:\u002F\u002Fgithub.com\u002Fsameersbn))\n\nSee [Contributors](..\u002F..\u002Fgraphs\u002Fcontributors) for the complete list developers that have contributed to this project.\n\n## Issues\n\nDocker is actively being developed and tested by a thriving community of developers and testers and every release of Docker features many enhancements and bugfixes.\n\nGiven 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.\n\nInstall the most recent version of the Docker Engine for your platform using the [official Docker releases](http:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstallation\u002F), which can also be installed using:\n\n```bash\nwget -qO- https:\u002F\u002Fget.docker.com\u002F | sh\n```\n\nFedora and RHEL\u002FCentOS 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.\n\nYou may also set `DEBUG=true` to enable debugging of the entrypoint script, which could help you pinpoint any configuration issues.\n\nIf using the latest docker version and\u002For disabling selinux does not fix the issue then please file an issue request on the [issues](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-gitlab\u002Fissues) page.\n\nIn your issue report please make sure you provide the following information:\n\n- The host distribution and release version.\n- Output of the `docker version` command\n- Output of the `docker info` command\n- The `docker run` command you used to run the image (mask out the sensitive bits).\n\n## Prerequisites\n\nYour docker host needs to have 1GB or more of available RAM to run GitLab. Please refer to the GitLab [hardware requirements](https:\u002F\u002Fgithub.com\u002Fgitlabhq\u002Fgitlabhq\u002Fblob\u002Fmaster\u002Fdoc\u002Finstall\u002Frequirements.md#hardware-requirements) documentation for additional information.\n\n## Installation\n\nAutomated builds of the image are available on [Dockerhub](https:\u002F\u002Fhub.docker.com\u002Fr\u002Fsameersbn\u002Fgitlab) and is the recommended method of installation.\n\n```bash\ndocker pull sameersbn\u002Fgitlab:18.11.2\n```\n\nYou can also pull the `latest` tag which is built from the repository *HEAD*\n\n```bash\ndocker pull sameersbn\u002Fgitlab:latest\n```\n\nAlternatively you can build the image locally.\n\n```bash\ndocker build -t sameersbn\u002Fgitlab github.com\u002Fsameersbn\u002Fdocker-gitlab\n```\n\n## Quick Start\n\nThe quickest way to get started is using [docker-compose](https:\u002F\u002Fdocs.docker.com\u002Fcompose\u002F).\n\n```bash\nwget https:\u002F\u002Fraw.githubusercontent.com\u002Fsameersbn\u002Fdocker-gitlab\u002Fmaster\u002Fdocker-compose.yml\n```\n\nGenerate 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:\n\n- `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.\n- `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.\n- `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.\n- `GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE` is used for reading settings from encrypted files such as SMTP or LDAP credentials.\n\n> **Tip**: You can generate a random string using `pwgen -Bsv1 64` and assign it as the value of `GITLAB_SECRETS_DB_KEY_BASE`.\n\nAlso generate random strings that are typically `32` characters long for each of:\n\n- `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY`\n- `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY`\n- `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT`\n\nThese values are used for `ActiveRecord::Encryption` encrypted columns. Details can be found under [Active Record Encryption](https:\u002F\u002Fguides.rubyonrails.org\u002Factive_record_encryption.html).\n\nStart GitLab using:\n\n```bash\ndocker-compose up\n```\n\nAlternatively, you can manually launch the `gitlab` container and the supporting `postgresql` and `redis` containers by following this three step guide.\n\nStep 1. Launch a postgresql container\n\n```bash\ndocker run --name gitlab-postgresql -d \\\n    --env 'DB_NAME=gitlabhq_production' \\\n    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \\\n    --env 'DB_EXTENSION=pg_trgm,btree_gist' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fpostgresql:\u002Fvar\u002Flib\u002Fpostgresql \\\n    kkimurak\u002Fsameersbn-postgresql:16\n```\n\nStep 2. Launch a redis container\n\n```bash\ndocker run --name gitlab-redis -d \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fredis:\u002Fdata \\\n    redis:7\n```\n\nStep 3. Launch the gitlab container\n\n```bash\ndocker run --name gitlab -d \\\n    --link gitlab-postgresql:postgresql --link gitlab-redis:redisio \\\n    --publish 10022:22 --publish 10080:80 \\\n    --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' \\\n    --env 'GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alpha-numeric-string' \\\n    --env 'GITLAB_SECRETS_SECRET_KEY_BASE=long-and-random-alpha-numeric-string' \\\n    --env 'GITLAB_SECRETS_OTP_KEY_BASE=long-and-random-alpha-numeric-string' \\\n    --env 'GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE=long-and-random-alpha-numeric-string' \\\n    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY=[\"long-and-random-alpha-numeric-string\"]' \\\n    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY=[\"long-and-random-alpha-numeric-string\"]' \\\n    --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT=long-and-random-alpha-numeric-string' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\n*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*\n\n**NOTE**: Please allow a couple of minutes for the GitLab application to start.\n\nPoint your browser to `http:\u002F\u002Flocalhost:10080` and set a password for the `root` user account.\n\nYou should now have the GitLab application up and ready for testing. If you want to use this image in production then please read on.\n\n*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.*\n\n## Configuration\n\n### Data Store\n\nGitLab is a code hosting software and as such you don't want to lose your code when the docker container is stopped\u002Fdeleted. To avoid losing any data, you should mount a volume at,\n\n- `\u002Fhome\u002Fgit\u002Fdata`\n\n*Note: that if you are using the `docker-compose` approach, you must \"inspect\" the volumes (```docker volume inspect```) to check the mounted path.*\n\nSELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.\n\n```bash\nmkdir -p \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\nsudo chcon -Rt svirt_sandbox_file_t \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\n```\n\nVolumes can be mounted in docker by specifying the `-v` option in the docker run command.\n\n```bash\ndocker run --name gitlab -d \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\n### Database\n\nGitLab uses a database backend to store its data. You can configure this image to use PostgreSQL.\n\n*Note:* GitLab requires PostgreSQL now. So use an older image \u003C 12.1 or migrate to PostgresSQL\n\n#### PostgreSQL\n\n**Important note:** This image is shipped with different versions of the `postgresql-client`.\n\nDuring 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.\n\nThis behavior can be checked using the command `docker logs` and an output like the following should be available:\n\n````sh\n…\nConfiguring gitlab::database\n- Installing postgresql client to avoid version mismatch on dumping\n-- Detected server version: 160009\n- Generating \u002Fhome\u002Fgit\u002F.postgresqlrc\n16 postgresql:5432 gitlabhq_production\n- Uninstalling unused client(s): postgresql-client-13 postgresql-client-14 postgresql-client-15 postgresql-client-17\n…\n````\n\nPlease note furthermore, that only compatible versions of the `postgresql-client` to GitLab are shipped with this image. Currently, these belong to\n\n- `postgresql-client-13`,\n- `postgresql-client-14`,\n- `postgresql-client-15`,\n- `postgresql-client-16`,\n- and `postgresql-client-17`.\n\n***Notes:***\n\n- GitLab CE version 13.7.0 and later requires PostgreSQL version 12.x.\n- GitLab CE version 16.0.0 and later requires PostgreSQL version 13.x.\n- GitLab CE version 17.0.0 and later requires PostgreSQL version 14.x.\n- GitLab CE version 18.0.0 and later requires PostgreSQL version 16.x.\n\n##### External PostgreSQL Server\n\nThe image also supports using an external PostgreSQL Server. This is also controlled via environment variables.\n\n```sql\nCREATE ROLE gitlab with LOGIN CREATEDB PASSWORD 'password';\nCREATE DATABASE gitlabhq_production;\nGRANT ALL PRIVILEGES ON DATABASE gitlabhq_production to gitlab;\n```\n\nAdditionally, since GitLab `8.6.0` the `pg_trgm` extension should also be loaded for the `gitlabhq_production` database.\n\nWe are now ready to start the GitLab application.\n\n*Note:* The following applies assuming that the PostgreSQL server host is `192.168.1.100`.\n\n```bash\ndocker run --name gitlab -d \\\n    --env 'DB_HOST=192.168.1.100' \\\n    --env 'DB_NAME=gitlabhq_production' \\\n    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\n##### Linking to PostgreSQL Container\n\nYou 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.\n\nIf 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.\n\nTo illustrate linking with a postgresql container, we will use the [sameersbn\u002Fpostgresql](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-postgresql) image. When using postgresql image in production you should mount a volume for the postgresql data store. Please refer the [README](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-postgresql\u002Fblob\u002Fmaster\u002FREADME.md) of docker-postgresql for details.\n\nFirst, let's pull the postgresql image from the docker index.\n\n```bash\ndocker pull kkimurak\u002Fsameersbn-postgresql:16\n```\n\nFor data persistence lets create a store for the postgresql and start the container.\n\nSELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.\n\n```bash\nmkdir -p \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fpostgresql\nsudo chcon -Rt svirt_sandbox_file_t \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fpostgresql\n```\n\nThe run command looks like this.\n\n```bash\ndocker run --name gitlab-postgresql -d \\\n    --env 'DB_NAME=gitlabhq_production' \\\n    --env 'DB_USER=gitlab' --env 'DB_PASS=password' \\\n    --env 'DB_EXTENSION=pg_trgm' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fpostgresql:\u002Fvar\u002Flib\u002Fpostgresql \\\n    kkimurak\u002Fsameersbn-postgresql:16\n```\n\nThe 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.\n\nWe are now ready to start the GitLab application.\n\n```bash\ndocker run --name gitlab -d --link gitlab-postgresql:postgresql \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nHere 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:\n\n- [postgres](https:\u002F\u002Fhub.docker.com\u002F_\u002Fpostgres\u002F),\n- [kkimurak\u002Fsameersbn-postgresql](https:\u002F\u002Fhub.docker.com\u002Fr\u002Fkkimurak\u002Fsameersbn-postgresql), or\n- [sameersbn\u002Fpostgresql](https:\u002F\u002Fquay.io\u002Frepository\u002Fsameersbn\u002Fpostgresql\u002F) .\n\n##### Upgrading PostgreSQL\n\nWhen this Gitlab image upgrades its dependency on specific version of PostgreSQL you will need to make sure to use corresponding version of PostgreSQL.\n\nIf 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.\n\nIf you are using PostgreSQL image other than [sameersbn\u002Fpostgresql](https:\u002F\u002Fquay.io\u002Frepository\u002Fsameersbn\u002Fpostgresql\u002F) 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.\n\nFollowing project provides Docker image that handles migration of PostgreSQL data: [tianon\u002Fpostgres-upgrade](https:\u002F\u002Fhub.docker.com\u002Fr\u002Ftianon\u002Fpostgres-upgrade\u002F)\n\nAfter 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.\n\n### Redis\n\nGitLab uses the redis server for its key-value data store. The redis server connection details can be specified using environment variables.\n\n#### Internal Redis Server\n\nThe internal redis server has been removed from the image. Please use a [linked redis](#linking-to-redis-container) container or specify a [external redis](#external-redis-server) connection.\n\n#### External Redis Server\n\nThe image can be configured to use an external redis server. The configuration should be specified using environment variables while starting the GitLab image.\n\n*Note:* The following applies assuming that the redis server host is `192.168.1.100`.\n\n```bash\ndocker run --name gitlab -it --rm \\\n    --env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\n#### Linking to Redis Container\n\nYou 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.\n\nTo illustrate linking with a redis container, we will use the [redis](https:\u002F\u002Fgithub.com\u002Fdocker-library\u002Fredis) image. Please refer the [README](https:\u002F\u002Fgithub.com\u002Fdocker-library\u002Fdocs\u002Fblob\u002Fmaster\u002Fredis\u002FREADME.md) for details.\n\nFirst, let's pull the redis image from the docker index.\n\n```bash\ndocker pull redis:7\n```\n\nLets start the redis container\n\n```bash\ndocker run --name gitlab-redis -d \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fredis:\u002Fdata \\\n    redis:7\n```\n\nWe are now ready to start the GitLab application.\n\n```bash\ndocker run --name gitlab -d --link gitlab-redis:redisio \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\n#### Mail\n\nThe 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.\n\nIf you are using Gmail then all you need to do is:\n\n```bash\ndocker run --name gitlab -d \\\n    --env 'SMTP_USER=USER@gmail.com' --env 'SMTP_PASS=PASSWORD' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nPlease refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.\n\n##### Microsoft Graph Mailer\n\nAs 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.\n\nTo 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:\n\n```bash\ndocker run --name gitlab -d \\\n    --env 'MICROSOFT_GRAPH_MAILER_ENABLED=true' \\\n    --env 'MICROSOFT_GRAPH_MAILER_USER_ID=00000000-0000-0000-0000-000000000000' \\\n    --env 'MICROSOFT_GRAPH_MAILER_TENANT=contoso.onmicrosoft.com' \\\n    --env 'MICROSOFT_GRAPH_MAILER_CLIENT_ID=11111111-1111-1111-1111-111111111111' \\\n    --env 'MICROSOFT_GRAPH_MAILER_CLIENT_SECRET=YOUR_CLIENT_SECRET' \\\n    --env 'GITLAB_EMAIL=sender@contoso.com' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.0\n```\n\n`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](#available-configuration-parameters) section for the list of Microsoft Graph Mailer parameters that can be specified.\n\n##### Reply by email\n\nSince version `8.0.0` GitLab adds support for commenting on issues by replying to emails.\n\nTo 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`.\n\nIf your email provider supports email [sub-addressing](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEmail_address#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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fincoming_email\u002FREADME.html) to understand the requirements for this feature.\n\nIf you are using Gmail then all you need to do is:\n\n```bash\ndocker run --name gitlab -d \\\n    --env 'IMAP_USER=USER@gmail.com' --env 'IMAP_PASS=PASSWORD' \\\n    --env 'GITLAB_INCOMING_EMAIL_ADDRESS=USER+%{key}@gmail.com' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nPlease refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.\n\n#### SSL\n\nAccess 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.\n\nJump to the [Using HTTPS with a load balancer](#using-https-with-a-load-balancer) section if you are using a load balancer such as hipache, haproxy or nginx.\n\nTo secure your application via SSL you basically need two things:\n\n- **Private key (.key)**\n- **SSL certificate (.crt)**\n\nWhen 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](#strengthening-the-server-security) section if you are armed with CA certified SSL certificates.\n\n##### Generation of a Self Signed Certificate\n\nGeneration of a self-signed SSL certificate involves a simple 3-step procedure:\n\n**STEP 1**: Create the server private key\n\n```bash\nopenssl genrsa -out gitlab.key 2048\n```\n\n**STEP 2**: Create the certificate signing request (CSR)\n\n```bash\nopenssl req -new -key gitlab.key -out gitlab.csr\n```\n\n**STEP 3**: Sign the certificate using the private key and CSR\n\n```bash\nopenssl x509 -req -days 3650 -in gitlab.csr -signkey gitlab.key -out gitlab.crt\n```\n\nCongratulations! You now have a self-signed SSL certificate valid for 10 years.\n\n##### Strengthening the server security\n\nThis section provides you with instructions to [strengthen your server security](https:\u002F\u002Fraymii.org\u002Fs\u002Ftutorials\u002FStrong_SSL_Security_On_nginx.html). To achieve this we need to generate stronger DHE parameters.\n\n```bash\nopenssl dhparam -out dhparam.pem 2048\n```\n\n##### Installation of the SSL Certificates\n\nOut 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).\n\nThe default path that the gitlab application is configured to look for the SSL certificates is at `\u002Fhome\u002Fgit\u002Fdata\u002Fcerts`, this can however be changed using the `SSL_KEY_PATH`, `SSL_CERTIFICATE_PATH` and `SSL_DHPARAM_PATH` configuration options.\n\nIf you remember from above, the `\u002Fhome\u002Fgit\u002Fdata` path is the path of the [data store](#data-store), which means that we have to create a folder named `certs\u002F` inside the volume to where `\u002Fhome\u002Fgit\u002Fdata` 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.\n\nIn case use of docker-compose ...\n\n```$>docker volume inspect```\n\nLook for \"\u003C user >_gitlab-data\" and copy the \"certs\" directory into the \"Mountpoint\"\n\n```bash\nmkdir -p \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\u002Fcerts\ncp gitlab.key \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\u002Fcerts\u002F\ncp gitlab.crt \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\u002Fcerts\u002F\ncp dhparam.pem \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\u002Fcerts\u002F\nchmod 400 \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab\u002Fcerts\u002Fgitlab.key\n```\n\nGreat! We are now just one step away from having our application secured.\n\n##### Enabling HTTPS support\n\nHTTPS 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\n\n```bash\ndocker run --name gitlab -d \\\n    --publish 10022:22 --publish 10080:80 --publish 10443:443 \\\n    --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=10443' \\\n    --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nIn 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.\n\n##### Configuring HSTS\n\nHSTS 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.\n\nWith `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`.\n\n```bash\ndocker run --name gitlab -d \\\n --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \\\n --env 'NGINX_HSTS_MAXAGE=2592000' \\\n --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n sameersbn\u002Fgitlab:18.11.2\n```\n\nIf you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.\n\n##### Using HTTPS with a load balancer\n\nLoad balancers like nginx\u002Fhaproxy\u002Fhipache 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.\n\nHowever, 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.\n\nWith 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\u002FHTTPS with HAProxy](http:\u002F\u002Fseanmcgary.com\u002Fposts\u002Fusing-sslhttps-with-haproxy) for information on the subject.\n\nWhen 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.\n\nIn summation, when using a load balancer, the docker command would look for the most part something like this:\n\n```bash\ndocker run --name gitlab -d \\\n    --publish 10022:22 --publish 10080:80 \\\n    --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=443' \\\n    --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nAgain, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates.\n\nIn 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:\n\n`proxy_set_header X-Forwarded-Ssl on;` (nginx format)\n\n##### Establishing trust with your server\n\nThis section deals will self-signed ssl certificates. If you are using CA certified certificates, you're done.\n\nThis 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.\n\nThis 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 `\u002Fusr\u002Flocal\u002Fshare\u002Fca-certificates\u002F` and executing `update-ca-certificates`.\n\nAgain, 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:\n\n```bash\ngit clone https:\u002F\u002Fgit.local.host\u002Fgitlab-foss.git\nfatal: unable to access 'https:\u002F\u002Fgit.local.host\u002Fgitlab-foss.git': server certificate verification failed. CAfile: \u002Fetc\u002Fssl\u002Fcerts\u002Fca-certificates.crt CRLfile: none\n```\n\nYou can do the same at the web browser. Instructions for installing the root certificate for firefox can be found [here](http:\u002F\u002Fportal.threatpulse.com\u002Fdocs\u002Fsol\u002FContent\u002F03Solutions\u002FManagePolicy\u002FSSL\u002Fssl_firefox_cert_ta.htm). You will find similar options chrome, just make sure you install the certificate under the authorities tab of the certificate manager dialog.\n\nThere you have it, that's all there is to it.\n\n##### Installing Trusted SSL Server Certificates\n\nIf 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.\n\nThe default path image is configured to look for the trusted SSL certificates is at `\u002Fhome\u002Fgit\u002Fdata\u002Fcerts\u002Fca.crt`, this can however be changed using the `SSL_CA_CERTIFICATES_PATH` configuration option.\n\nCopy the `ca.crt` file into the certs directory on the [datastore](#data-store). 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](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-gitlab-ci\u002Fblob\u002Fmaster\u002FREADME.md#ssl) of the [docker-gitlab-ci](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-gitlab-ci) container.\n\nBy default, our own server certificate [gitlab.crt](#generation-of-a-self-signed-certificate) is added to the trusted certificates list.\n\n#### Deploy to a subdirectory (relative url root)\n\nBy default, GitLab expects that your application is running at the root (e.g.. \u002F). This section explains how to run your application inside a directory.\n\nLet's assume we want to deploy our application to '\u002Fgit'. 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:\n\n```bash\ndocker run --name gitlab -it --rm \\\n    --env 'GITLAB_RELATIVE_URL_ROOT=\u002Fgit' \\\n    --volume \u002Fsrv\u002Fdocker\u002Fgitlab\u002Fgitlab:\u002Fhome\u002Fgit\u002Fdata \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nGitLab will now be accessible at the `\u002Fgit` path, e.g. `http:\u002F\u002Fwww.example.com\u002Fgit`.\n\n**Note**: *The `GITLAB_RELATIVE_URL_ROOT` parameter should always begin with a slash and* **SHOULD NOT** *have any trailing slashes.*\n\n#### OmniAuth Integration\n\nGitLab 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.\n\nRefer to the GitLab [documentation](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fomniauth.html) for additional information.\n\n##### CAS3\n\nTo 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:\u002F\u002Fgit.example.com:443\u002Fusers\u002Fauth\u002Fcas3\u002Fcallback?url`. By default handling for SLO is enabled, you only need to configure CAS for backchannel logout.\n\nFor example, if your cas server url is `https:\u002F\u002Fsso.example.com`, then adding `--env 'OAUTH_CAS3_SERVER=https:\u002F\u002Fsso.example.com'` to the docker run command enables support for CAS3 OAuth. Please refer to [Available Configuration Parameters](#available-configuration-parameters) for additional CAS3 configuration parameters.\n\n##### Authentiq\n\nTo enable the Authentiq OmniAuth provider for passwordless authentication you must register an application with [Authentiq](https:\u002F\u002Fwww.authentiq.com\u002F). Please refer to the GitLab [documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fce\u002Fadministration\u002Fauth\u002Fauthentiq.html) for the procedure to generate the client ID and secret key with Authentiq.\n\nOnce 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.\n\nFor 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.\n\nYou 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'`).\n\n##### Google\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fgoogle.html) for the procedure to generate the client ID and secret key with google.\n\nOnce 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.\n\nFor 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.\n\nYou can also restrict logins to a single domain by adding `--env \"OAUTH_GOOGLE_RESTRICT_DOMAIN='example.com'\"`.\n\n##### Facebook\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Ffacebook.html) for the procedure to generate the API key and secret.\n\nOnce you have the API key and secret generated, configure them using the `OAUTH_FACEBOOK_API_KEY` and `OAUTH_FACEBOOK_APP_SECRET` environment variables respectively.\n\nFor 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.\n\n##### Twitter\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Ftwitter.html) for the procedure to generate the API key and secret with twitter.\n\nOnce you have the API key and secret generated, configure them using the `OAUTH_TWITTER_API_KEY` and `OAUTH_TWITTER_APP_SECRET` environment variables respectively.\n\nFor 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.\n\n##### GitHub\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fgithub.html) for the procedure to generate the Client ID and secret with github.\n\nOnce you have the Client ID and secret generated, configure them using the `OAUTH_GITHUB_API_KEY` and `OAUTH_GITHUB_APP_SECRET` environment variables respectively.\n\nFor 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.\n\nUsers of GitHub Enterprise may want to specify `OAUTH_GITHUB_URL` and `OAUTH_GITHUB_VERIFY_SSL` as well.\n\n##### GitLab\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fgitlab.html) for the procedure to generate the Client ID and secret with GitLab.\n\nOnce you have the Client ID and secret generated, configure them using the `OAUTH_GITLAB_API_KEY` and `OAUTH_GITLAB_APP_SECRET` environment variables respectively.\n\nFor 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.\n\n##### BitBucket\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fbitbucket.html) for the procedure to generate the Client ID and secret with BitBucket.\n\nOnce you have the Client ID and secret generated, configure them using the `OAUTH_BITBUCKET_API_KEY` and `OAUTH_BITBUCKET_APP_SECRET` environment variables respectively.\n\nFor 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.\n\n##### SAML\n\nGitLab 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fsaml.html).\n\nThe 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`.\n\nYou can also override the default \"Sign in with\" button label with `OAUTH_SAML_LABEL`.\n\nPlease refer to [Available Configuration Parameters](#available-configuration-parameters) for the default configurations of these parameters.\n\n##### Crowd\n\nTo enable the Crowd server OAuth2 OmniAuth provider you must register your application with Crowd server.\n\nConfigure 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.\n\n##### Auth0\n\nTo enable the Auth0 OmniAuth provider you must register your application with [auth0](https:\u002F\u002Fauth0.com\u002F).\n\nConfigure the following environment variables `OAUTH_AUTH0_CLIENT_ID`, `OAUTH_AUTH0_CLIENT_SECRET` and `OAUTH_AUTH0_DOMAIN` to complete the integration.\n\n##### Microsoft Azure\n\nTo 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](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fintegration\u002Fazure.html) for the procedure.\n\nOnce 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.\n\nFor 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.\n\nAlso 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`.\n\n##### Generic OAuth2\n\nTo 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.\n\nAs 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`.\n\nSee [GitLab documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fintegration\u002Foauth2_generic.html#sign-into-gitlab-with-almost-any-oauth2-provider) and [Omniauth-oauth2-generic documentation](https:\u002F\u002Fgitlab.com\u002Fsatorix\u002Fomniauth-oauth2-generic) for more details.\n\n##### OpenID Connect\n\nTo 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.\n\nTo use OIDC set at least `OAUTH_OIDC_ISSUER` and `OAUTH_OIDC_CLIENT_ID`.\n\n| GitLab setting                 | environment variable                | default value                  |\n|--------------------------------|-------------------------------------|--------------------------------|\n| `label`                        | `OAUTH_OIDC_LABEL`                  | `OpenID Connect`               |\n| `icon`                         | `OAUTH_OIDC_ICON`                   |                                |\n| `scope`                        | `OAUTH_OIDC_SCOPE`                  | `['openid','profile','email']` |\n| `response_type`                | `OAUTH_OIDC_RESPONSE_TYPE`          | `code`                         |\n| `issuer`                       | `OAUTH_OIDC_ISSUER`                 |                                |\n| `discovery`                    | `OAUTH_OIDC_DISCOVERY`              | `true`                         |\n| `client_auth_method`           | `OAUTH_OIDC_CLIENT_AUTH_METHOD`     | `basic`                        |\n| `uid_field`                    | `OAUTH_OIDC_UID_FIELD`              | `sub`                          |\n| `send_scope_to_token_endpoint` | `OAUTH_OIDC_SEND_SCOPE_TO_TOKEN_EP` | `false`                        |\n| `pkce`                         | `OAUTH_OIDC_PKCE`                   | `true`                         |\n| `client_options.identifier`    | `OAUTH_OIDC_CLIENT_ID`              |                                |\n| `client_options.secret`        | `OAUTH_OIDC_CLIENT_SECRET`          | `secret`                       |\n| `client_options.redirect_uri`  | `OAUTH_OIDC_REDIRECT_URI`           | `http:\u002F\u002F${GITLAB_HOST}\u002Fusers\u002Fauth\u002Fopenid_connect\u002Fcallback` or `https:\u002F\u002F${GITLAB_HOST}\u002Fusers\u002Fauth\u002Fopenid_connect\u002Fcallback` depending on the value of `GITLAB_HTTPS` |\n\nSee [GitLab OIDC documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fadministration\u002Fauth\u002Foidc.html) and [OmniAuth OpenID Connect documentation](https:\u002F\u002Fgithub.com\u002Fomniauth\u002Fomniauth_openid_connect\u002F).\n\n##### JWT\n\nTo enable the JWT OmniAuth provider, you must register your application with JWT. JWT provides you with a secret key for you to use.\n\nTo use JWT set at least `OAUTH_JWT_SECRET` and `OAUTH_JWT_AUTH_URL`.\n\n| GitLab setting                 | environment variable                | default value                  |\n| ------------------------------ | ----------------------------------- | -------------------------------|\n| `label`                        | `OAUTH_JWT_LABEL`                   | `Jwt`                          |\n| `secret`                       | `OAUTH_JWT_SECRET`                  |                                |\n| `algorithm`                    | `OAUTH_JWT_ALGORITHM`               | `HS256`                        |\n| `uid_claim`                    | `OAUTH_JWT_UID_CLAIM`               | `email`                        |\n| `required_claims`              | `OAUTH_JWT_REQUIRED_CLAIMS`         | `[\"name\", \"email\"]`            |\n| `info_map.name`                | `OAUTH_JWT_INFO_MAP_NAME`           | `name`                         |\n| `info_map.email`               | `OAUTH_JWT_INFO_MAP_EMAIL`          | `email`                        |\n| `auth_url`                     | `OAUTH_JWT_AUTH_URL`                |                                |\n| `valid_within`                 | `OAUTH_JWT_VALID_WITHIN`            | `3600`                         |\n\n\nSee [OmniAuth JWT documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fadministration\u002Fauth\u002Fjwt\u002F).\n\n#### Gitlab Pages\n\nGitlab Pages allows a user to host static websites from a project. Gitlab pages can be enabled with setting the environment variable `GITLAB_PAGES_ENABLED` to `true`.\n\n#### Gitlab Pages Access Control\n\nSince version `11.5.0` Gitlab pages supports access control. This allows only access to a published website if you are a project member, or have access to a certain project.\n\nGitlab pages access control requires additional configuration before activating it through the variable `GITLAB_PAGES_ACCESS_CONTROL`.\n\nGitLab pages access control makes use of the Gitlab OAuth Module.\n\n- Goto the Gitlab Admin area\n- Select `Applications` in the menu\n- Create `New Application`\n    - Name: `Gitlab Pages`\n    - Scopes:\n        - api\n    - Trusted: NO (Do not select)\n    - Redirect URI: `https:\u002F\u002Fprojects.\u003CGITLAB_PAGES_DOMAIN>\u002Fauth`\n\nNote about the `Redirect URI`; this can be tricky to configure or figure out, What needs to be achieved is the following, the redirect URI needs to end up at the `gitlab-pages` daemon with the `\u002Fauth` endpoint.\n\nThis means that if you run your gitlab pages at domain `pages.example.io` this will be a wildcard domain where your projects are created based on their namespace. The best trick is to enter a NON-Existing gitlab project pages URI as the redirect URI.\n\nIn the example above; the pages domain `projects` has been chosen. This will cause the nginx, either the built in or your own load balancer to redirect `*.\u003CGITLAB_PAGES_DOMAIN>` to the `gitlab-pages` daemon. Which will trigger the pages endpoint.\n\nMake sure to choose own which does not exist and make sure that the request is routed to the `gitlab-pages` daemon if you are using your own HTTP load balancer in front of Gitlab.\n\nAfter creating the OAuth application endpoint for the Gitlab Pages Daemon. Gitlab pages access control can now be enabled.\n\nAdd to following environment variables to your Gitlab Container.\n\n| Variable | R\u002FO | Description |\n|----------|-----|-------------|\n| GITLAB_PAGES_ACCESS_CONTROL | Required | Set to `true` to enable access control. |\n| GITLAB_PAGES_ACCESS_SECRET | Optional | Secret Hash, minimal 32 characters, if omitted, it will be auto generated. |\n| GITLAB_PAGES_ACCESS_CONTROL_SERVER | Required | Gitlab instance URI, example: `https:\u002F\u002Fgitlab.example.io` |\n| GITLAB_PAGES_ACCESS_CLIENT_ID | Required | Client ID from earlier generated OAuth application |\n| GITLAB_PAGES_ACCESS_CLIENT_SECRET | Required | Client Secret from earlier generated OAuth application |\n| GITLAB_PAGES_ACCESS_REDIRECT_URI | Required | Redirect URI, non existing pages domain to redirect to pages daemon, `https:\u002F\u002Fprojects.example.io` |\n\nAfter you have enabled the gitlab pages access control. When you go to a project `General Settings` -> `Permissions` you can choose the pages permission level for the project.\n\n#### External Issue Trackers\n\nSince version `7.10.0` support for external issue trackers can be enabled in the \"Service Templates\" section of the settings panel.\n\nIf you are using the [docker-redmine](https:\u002F\u002Fgithub.com\u002Fsameersbn\u002Fdocker-redmine) image, you can *one up* the gitlab integration with redmine by adding `--volumes-from=gitlab` flag to the docker run command while starting the redmine container.\n\nBy using the above option the `\u002Fhome\u002Fgit\u002Fdata\u002Frepositories` directory will be accessible by the redmine container and now you can add your git repository path to your redmine project. If, for example, in your gitlab server you have a project named `opensource\u002Fgitlab`, the bare repository will be accessible at `\u002Fhome\u002Fgit\u002Fdata\u002Frepositories\u002Fopensource\u002Fgitlab.git` in the redmine container.\n\n#### Host UID \u002F GID Mapping\n\nPer default the container is configured to run gitlab as user and group `git` with `uid` and `gid` `1000`. The host possibly uses this ids for different purposes leading to unfavorable effects. From the host it appears as if the mounted data volumes are owned by the host's user\u002Fgroup `1000`.\n\nAlso the container processes seem to be executed as the host's user\u002Fgroup `1000`. The container can be configured to map the `uid` and `gid` of `git` to different ids on host by passing the environment variables `USERMAP_UID` and `USERMAP_GID`. The following command maps the ids to user and group `git` on the host.\n\n```bash\ndocker run --name gitlab -it --rm [options] \\\n    --env \"USERMAP_UID=$(id -u git)\" --env \"USERMAP_GID=$(id -g git)\" \\\n    sameersbn\u002Fgitlab:18.11.2\n```\n\nWhen changing this mapping, all files and directories in the mounted data volume `\u002Fhome\u002Fgit\u002Fdata` have to be re-owned by the new ids. This can be achieved automatically using the following command:\n\n```bash\ndocker run --name gitlab -d [OPTIONS] \\\n    sameersbn\u002Fgitlab:18.11.2 app:sanitize\n```\n\n#### Piwik\n\nIf you want to monitor your gitlab instance with [Piwik](http:\u002F\u002Fpiwik.org\u002F), there are two options to setup: `PIWIK_URL` and `PIWIK_SITE_ID`.\nThese options should contain something like:\n\n- `PIWIK_URL=piwik.example.org`\n- `PIWIK_SITE_ID=42`\n\n#### Feature flags\n\nIn this section, we talk about feature flags that administrators can change the state (See \u003Chttps:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fadministration\u002Ffeature_flags.html>). If you are looking for documentation for \"Feature flags\" that configured on project deploy settings, see \u003Chttps:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Foperations\u002Ffeature_flags.html>\n\nGitLab adopted feature flags strategies to deploy features in an early stage of development so that they can be incrementally rolled out. GitLab administrators with access to the [Rails console](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fadministration\u002Ffeature_flags.html#how-to-enable-and-disable-features-behind-flags) or the [Feature flags API](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fapi\u002Ffeatures.html) can control them (note that `sameersbn\u002Fgitlab` is a container image that provides GitLab installations from the source).\nYou can see all feature flags in GitLab at corresponding version of documentation: \u003Chttps:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Ffeature_flags.html>\n\nFor `sameersbn\u002Fgitlab`, you can control them via environment parameter [`GITLAB_FEATURE_FLAGS_DISABLE_TARGETS`](#gitlab_feature_flags_disable_targets) and [`GITLAB_FEATURE_FLAGS_ENABLE_TARGETS`](#gitlab_feature_flags_enable_targets) in addition to the above methods.\nThis image searches yml files in [`${GITLAB_INSTALL_DIR}\u002Fconfig\u002Ffeature_flags`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fgitlab-foss\u002F-\u002Ftree\u002Fmaster\u002Fconfig\u002Ffeature_flags) (typically `\u002Fhome\u002Fgit\u002Fgitlab\u002Fconfig\u002Ffeature_flags\u002F`) recursively and use the file list as a source of active feature flags.\n\nHere is a part of example `docker-compose.yml`:\n\n````yml\nservices:\n  gitlab:\n    image: sameersbn\u002Fgitlab:latest\n    environment:\n    - GITLAB_FEATURE_FLAGS_DISABLE_TARGETS=auto_devops_banner_disabled,ci_enable_live_trace\n    - GITLAB_FEATURE_FLAGS_ENABLE_TARGETS=git_push_create_all_pipelines,build_service_proxy\n````\n\nOnce the container up, you can see following messages in container log like below.\n\n````sh\n...\nConfiguring gitlab::feature_flags...\n- specified feature flags: {:to_be_disabled=>[\"auto_devops_banner_disabled\", \"ci_enable_live_trace\"], :to_be_enabled=>[\"git_push_create_all_pipelines\", \"build_service_proxy\"]}\n- auto_devops_banner_disabled : off\n- ci_enable_live_trace : off\n- git_push_create_all_pipelines : on\n- build_service_proxy : on\n...\n````\n\nIf specified flag names are not included in the list, they will be ignored and appears to container log like below:\n\n````sh\n...\nConfiguring gitlab::feature_flags...\n- specified feature flags: {:to_be_disabled=>[\"auto_devops_banner_disabled\", \"invalid_flag_name\"], :to_be_enabled=>[\"git_push_create_all_pipelines\", \"another_invalid_flag_name\"]}\n- Following flags are probably invalid and have been ignored: invalid_flag_name,another_invalid_flag_name\n- auto_devops_banner_disabled : off\n- git_push_create_all_pipelines : on\n...\n````\n\n#### Available Configuration Parameters\n\n*Please refer the docker run command options for the `--env-file` flag where you can specify all required environment variables in a single file. This will save you from writing a potentially long docker run command. Alternatively you can use docker-compose. docker-compose users and Docker Swarm mode users can also use the [secrets and config file options](#docker-secrets-and-configs)*\n\nBelow is the complete list of available options that can be used to customize your gitlab installation.\n\n##### `DEBUG`\n\nSet this to `true` to enable entrypoint debugging.\n\n##### `TZ`\n\nSet the container timezone. Defaults to `UTC`. Values are expected to be in Canonical format. Example: `Europe\u002FAmsterdam`  See the list of [acceptable values](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FList_of_tz_database_time_zones). For configuring the timezone of gitlab see variable `GITLAB_TIMEZONE`.\n\n##### `GITLAB_HOST`\n\nThe hostname of the GitLab server. Defaults to `localhost`\n\n##### `GITLAB_CI_HOST`\n\nIf you are migrating from GitLab CI use this parameter to configure the redirection to the GitLab service so that your existing runners continue to work without any changes. No defaults.\n\n##### `GITLAB_PORT`\n\nThe port of the GitLab server. This value indicates the public port on which the GitLab application will be accessible on the network and appropriately configures GitLab to generate the correct urls. It does not affect the port on which the internal nginx server will be listening on. Defaults to `443` if `GITLAB_HTTPS=true`, else defaults to `80`.\n\n##### `GITLAB_SECRETS_DB_KEY_BASE`\n\nEncryption key for GitLab CI secret variables, as well as import credentials, in the database. Ensure that your key is at least 32 characters long and that you don't lose it. You can generate one using `pwgen -Bsv1 64`. If you are migrating from GitLab CI, you need to set this value to the value of `GITLAB_CI_SECRETS_DB_KEY_BASE`. No defaults.\n\n##### `GITLAB_SECRETS_SECRET_KEY_BASE`\n\nEncryption key for session secrets. Ensure that your key is at least 64 characters long and that you don't lose it. This secret can be rotated with minimal impact - the main effect is that previously-sent password reset emails will no longer work. You can generate one using `pwgen -Bsv1 64`. No defaults.\n\n##### `GITLAB_SECRETS_OTP_KEY_BASE`\n\n Encryption key for OTP related stuff with  GitLab. Ensure that your key is at least 64 characters long and that you don't lose it. **If you lose or change this secret, 2FA will stop working for all users.** You can generate one using `pwgen -Bsv1 64`. No defaults.\n\n##### `GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE`\n\n Encryption key for encrypted settings related stuff with GitLab. Ensure that your key is at least 64 characters long and that you don't lose it. **If you lose or change this secret, encrypted settings will not work and might cause errors in merge requests and so on** You can generate one using `pwgen -Bsv1 64`. No defaults.\n\n##### `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY`\n\nThe base key used to encrypt data for non-deterministic `ActiveRecord::Encryption` encrypted columns. This value is used to set `active_record_encryption_primary_key` in `config\u002Fsecrets.yml`. Ensure that your key is an alphanumeric string. Preferred to be 32 characters long. If you need to set multiple keys, set this parameter in the format `[\"first_primary_key\",\"second_primary_key\"]`. In `docker-compose.yml`, the value must NOT have additional quotes! **If you lose or change this secret, encrypted settings will not work and might cause errors in the API and the web interface.** No defaults.\n\n##### `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY`\n\nThe base key used to encrypt data for deterministic `ActiveRecord::Encryption` encrypted columns. This value is used to set `active_record_encryption_deterministic_key` in `config\u002Fsecrets.yml`. Ensure that your key is an alphanumeric string. Preferred to be 32 characters long. If you need to set multiple keys, set this parameter in the format `[\"first_deterministic_key\",\"second_deterministic_key\"]`. In `docker-compose.yml`, the value must NOT have additional quotes! **If you lose or change this secret, encrypted settings will not work and might cause errors in the API and the web interface.** No defaults.\n\n##### `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT`\n\nThe salt used to encrypt data for `ActiveRecord::Encryption` encrypted columns. This value is used to set `active_record_encryption_key_derivation_salt` in `config\u002Fsecrets.yml`. Ensure that your salt is an alphanumeric string. Preferred to be 32 characters long. **If you lose or change this secret, encrypted settings will not work and might cause errors in the API and the web interface.** No defaults.\n\n##### `GITLAB_TIMEZONE`\n\nConfigure the timezone for the gitlab application. This configuration does not effect cron jobs. Defaults to `UTC`. See the list of [acceptable values](http:\u002F\u002Fapi.rubyonrails.org\u002Fclasses\u002FActiveSupport\u002FTimeZone.html). For settings the container timezone which will affect cron, see variable `TZ`\n\n##### `GITLAB_ROOT_PASSWORD`\n\nThe password for the root user on firstrun. Defaults to `5iveL!fe`. GitLab requires this to be at least **8 characters long**.\n\n##### `GITLAB_ROOT_EMAIL`\n\nThe email for the root user on firstrun. Defaults to `admin@example.com`\n\n##### `GITLAB_EMAIL`\n\nThe email address for the GitLab server. Defaults to value of `SMTP_USER`, else defaults to `example@example.com`.\n\n##### `GITLAB_EMAIL_DISPLAY_NAME`\n\nThe name displayed in emails sent out by the GitLab mailer. Defaults to `GitLab`.\n\n##### `GITLAB_EMAIL_REPLY_TO`\n\nThe reply-to address of emails sent out by GitLab. Defaults to value of `GITLAB_EMAIL`, else defaults to `noreply@example.com`.\n\n##### `GITLAB_EMAIL_SUBJECT_SUFFIX`\n\nThe e-mail subject suffix used in e-mails sent by GitLab. No defaults.\n\n##### `GITLAB_EMAIL_ENABLED`\n\nEnable or disable gitlab mailer. Defaults to the `SMTP_ENABLED` configuration.\n\n##### `GITLAB_EMAIL_SMIME_ENABLE`\n\nEnable or disable email S\u002FMIME signing. Defaults is `false`.\n\n##### `GITLAB_EMAIL_SMIME_KEY_FILE`\n\nSpecifies the path to a S\u002FMIME private key file in PEM format, unencrypted. Defaults to ``.\n\n##### `GITLAB_EMAIL_SMIME_CERT_FILE`\n\nSpecifies the path to a S\u002FMIME public certificate key in PEM format. Defaults to ``.\n\n##### `GITLAB_DEFAULT_THEME`\n\nDefault theme ID, by default 2. (1 - Indigo, 2 - Dark, 3 - Light, 4 - Blue, 5 - Green, 6 - Light Indigo, 7 - Light Blue, 8 - Light Green, 9 - Red, 10 - Light Red)\n\n##### `GITLAB_ISSUE_CLOSING_PATTERN`\n\nIssue closing pattern regex. See [GitLab's documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fadministration\u002Fissue_closing_pattern.html) for more detail. Defaults to ` \\b((?:[Cc]los(?:e[sd]?|ing)|\\b[Ff]ix(?:e[sd]|ing)?|\\b[Rr]esolv(?:e[sd]?|ing)|\\b[Ii]mplement(?:s|ed|ing)?)(:?) +(?:(?:issues? +)?%{issue_ref}(?:(?:, *| +and +)?)|([A-Z][A-Z0-9_]+-\\d+))+) ` .\n\n##### `GITLAB_INCOMING_EMAIL_ADDRESS`\n\nThe incoming email address for reply by email. Defaults to the value of `IMAP_USER`, else defaults to `reply@example.com`. Please read the [reply by email](http:\u002F\u002Fdoc.gitlab.com\u002Fce\u002Fincoming_email\u002FREADME.html) documentation to currently set this parameter.\n\n##### `GITLAB_INCOMING_EMAIL_ENABLED`\n\nEnable or disable gitlab reply by email feature. Defaults to the value of `IMAP_ENABLED`.\n\n##### `GITLAB_SIGNUP_ENABLED`\n\nEnable or disable user signups (first run only). Default is `true`.\n\n##### `GITLAB_IMPERSONATION_ENABLED`\n\nEnable or disable impersonation. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_LIMIT`\n\nSet default projects limit. Defaults to `100`.\n\n##### `GITLAB_USERNAME_CHANGE`\n\nEnable or disable ability for users to change their username. Defaults to `true`.\n\n##### `GITLAB_CREATE_GROUP`\n\nEnable or disable ability for users to create groups. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_ISSUES`\n\nSet if *issues* feature should be enabled by default for new projects. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_MERGE_REQUESTS`\n\nSet if *merge requests* feature should be enabled by default for new projects. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_WIKI`\n\nSet if *wiki* feature should be enabled by default for new projects. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_SNIPPETS`\n\nSet if *snippets* feature should be enabled by default for new projects. Defaults to `false`.\n\n##### `GITLAB_PROJECTS_BUILDS`\n\nSet if *builds* feature should be enabled by default for new projects. Defaults to `true`.\n\n##### `GITLAB_PROJECTS_CONTAINER_REGISTRY`\n\nSet if *container_registry* feature should be enabled by default for new projects. Defaults to `true`.\n\n##### `GITLAB_SHELL_CUSTOM_HOOKS_DIR`\n\nGlobal custom hooks directory. Defaults to `\u002Fhome\u002Fgit\u002Fgitlab-shell\u002Fhooks`.\n\n##### `GITLAB_WEBHOOK_TIMEOUT`\n\nSets the timeout for webhooks. Defaults to `10` seconds.\n\n##### `GITLAB_NOTIFY_ON_BROKEN_BUILDS`\n\nEnable or disable broken build notification emails. Defaults to `true`\n\n##### `GITLAB_NOTIFY_PUSHER`\n\nAdd pusher to recipients list of broken build notification emails. Defaults to `false`\n\n##### `GITLAB_REPOS_DIR`\n\nThe git repositories folder in the container. Defaults to `\u002Fhome\u002Fgit\u002Fdata\u002Frepositories`\n\n##### `GITLAB_BACKUP_DIR`\n\nThe backup folder in the container. Defaults to `\u002Fhome\u002Fgit\u002Fdata\u002Fbackups`\n\n##### `GITLAB_BACKUP_DIR_CHOWN`\n\nOptionally change ownership of backup files on start-up. Defaults to `true`\n\n##### `GITLAB_BACKUP_DIR_GROUP`\n\nOptionally group backups into a subfolder. Can also be used to place backups in to a subfolder on remote storage. Not used by default.\n\n##### `GITLAB_BUILDS_DIR`\n\nThe build traces directory. Defaults to `\u002Fhome\u002Fgit\u002Fdata\u002Fbuilds`\n\n##### `GITLAB_DOWNLOADS_DIR`\n\nThe repository downloads directory. A temporary zip is created in this directory when users click **Download Zip** on a project. Defaults to `\u002Fhome\u002Fgit\u002Fdata\u002Ftmp\u002Fdownloads`.\n\n##### `GITLAB_SHARED_DIR`\n\nThe directory to store the build artifacts. Defaults to `\u002Fhome\u002Fgit\u002Fdata\u002Fshared`\n\n##### `GITLAB_ARTIFACTS_ENABLED`\n\nEnable\u002FDisable GitLab artifacts support. Defaults to `true`.\n\n##### `GITLAB_ARTIFACTS_DIR`\n\nDirectory to store the artifacts. Defaults to `$GITLAB_SHARED_DIR\u002Fartifacts`\n\n##### `AWS_ACCESS_KEY_ID`\n\nDefault AWS access key to be used for object store. Defaults to `AWS_ACCESS_KEY_ID`\n\n##### `AWS_SECRET_ACCESS_KEY`\n\nDefault AWS access key to be used for object store. Defaults to `AWS_SECRET_ACCESS_KEY`\n\n##### `AWS_REGION`\n\nAWS Region. Defaults to `us-east-1`\n\n##### `AWS_HOST`\n\nConfigure this for an compatible AWS host like minio. Defaults to `$AWS_HOST`. Defaults to `s3.amazon.com`\n\n##### `AWS_ENDPOINT`\n\nAWS Endpoint like `http:\u002F\u002F127.0.0.1:9000`. De","sameersbn\u002Fdocker-gitlab 项目提供了一个基于 Docker 的 GitLab 容器化解决方案。它支持多种配置选项，包括数据存储、数据库（推荐使用 PostgreSQL）、Redis 服务器、邮件服务以及 SSL 证书的安装与 HTTPS 支持等，从而确保了高度可定制性和安全性。此外，该项目还集成了 OAuth2、SAML 等多种认证方式，并支持 GitLab Pages 功能。适用于需要快速部署 GitLab 实例且希望利用 Docker 简化运维流程的企业或个人开发者，在开发测试环境搭建、持续集成\u002F持续部署(CI\u002FCD)流水线构建等场景中尤为适用。","2026-06-11 03:26:02","top_topic"]