Install Gitlab With Docker

  1. Install Gitlab With Docker Windows
  2. Install Gitlab With Docker Linux
  3. Install Gitlab With Docker Software
  4. Install Gitlab With Docker

Install Gitlab CE in Docker. Here is the official Gitlab Docker doc, I really thank the Gitlab team, their doc system is one of the bests that I’ve ever seen. Another doc from IBM is also good. Run the following commands to install Gitlab-CE in Docker. Get Social!Create a new directory and save the above file inside it as docker-compose.yml. You’ll need to replace the field hostname with the external URL that you’ll use to access your Gitlab instance. Run docker-compose up -d to fetch the images from the docker hub and create your Gitlab instance. You’ll be able to access.

Today I installed the GitLab Community Edition on Docker. It takes me some time to figure out how to get it done in an reasonable way. On the GitLab pages there is an installation guide for Docker. And the Docker images for GitLab are very well maintained on DockerHub. In the following I will expalin how to run GitLab with Docker-Compose and separate Database Containers.

Additionally, there are manual instructions on how to setup Gitlab runners on Ubuntu 20.04, Ubuntu 20.04 with Docker, Windows 10, Windows 10 with Docker, and macOS Big Sur. In addition, a Docker Registry is setup and integrated into the CI/CD pipeline for custom Docker images. The instructions and the infra-as-code provided in this post will. The GitLab Docker images are monolithic images of GitLab running all the necessary services in a single container. If you instead want to install GitLab on Kubernetes, see GitLab Helm Charts. Find the GitLab official Docker image at: GitLab Docker image in Docker Hub. The Docker images don’t include a mail transport agent (MTA).

If you follow the install guide you can start a GitLab Container from the command line or with Docker compose. However, the examples are not representative of how you may run GitLab in your production environment. GitLab comes with a so called all-on-one Docker container. The image contains beside the GitLab applicaton also a Redis and a PostgreSQL database. This is convenient for a first look but not the best setup for docker.

Use Docker-Compose

If you were going to run it in a docker environment like Imixs-Cloud, you’d may want to use external data services for PostgreSQL and Redis, as well as store the GitLab filesystem somewhere that will persist. Thankfully, the GitLab CE Docker image makes it easy to do these things. In the following example I show how you can setup GitLab with Docker Compose. This example can also be adapted to Docker Swarm. In the docker-compose file I split the Redis and PostgreSQL database into separate containers. There for you need to deactivate the internal databases. All configuration settings can be done in the environment variable named ‘GITLAB_OMNIBUS_CONFIG.

Note: The ‘external_url’ is optional and not necessary for local testing.


During my first tests I run into some strange behavior when the Docker-Container wont start any more. To solve such a situation its best to remove the existing containers and start again. Especially the configuration data located in /etc/gitlab can be a cause for a problem.

Additional Notes

The Admin Account

After the first launch you will be asked to create the admin password. You can later login with the userid ‘root’ and you admin password to administrate your environment


You can run GitLab also in combination with Traefik reverse-proxy. In case you use Traefik with HTTPS and self-signed certificates you need to disable this feature in GitLab. Set the following GITLAB_OMNIBUS_CONFIG entry:

In addition you may not set the parameter ‘external_url’, so just uncomment. Also it is necessary to add the Hostname into your service description. Otherwise the Repository URLs generated by GitLab will show the correct external address. Here is the complete configuration example in case of traefik:

Disabling Prometheus

For some reasons the GitLab Image includes not only the database server but also a Prometheus installation. I do not understand why this is possible. It takes much rescources. To disable it add the following GITLAB_OMNIBUS_CONFIG entry:


How to Create Backups

You can easily backup your GitLab data with the build in backup tool:

The backups will be stored at:

Install Gitlab Ce Docker Free

Note: The backup does not include the configuration files or SSL certificates. So it is necessary to backup also the folder:

Comments are closed.

docker install

Install git, docker and docker-compose.
Note: don't forget docker's post-installation steps! (eg for linux).

Install Gitlab With Docker Windows

Fetch the source:

Copy the environement variables file

Change some of those variables if you wish to,
notably the super-user username and password are created from DJANGO_SU_NAME and DJANGO_SU_PASSWORD, defaulting to admin:admin.

Install Gitlab With Docker Linux

Build and run the docker containers

You should be able to access the website at http://localhost:8080/

To update:

Use your GPU:

Install Gitlab With Docker Software

  1. Install cuda & cudnn
  2. Create a file named local.yml with this content

Install Gitlab With Docker

  1. When you build use both yml files
  • Most Viewed News

    • Google Maps Macos
    • Slack Osx
    • Install Python 3.7 Docker
    • Clean App Mac