From c3fbbb5da3f8f787e6dce09d7e6cc7b22bd24b3d Mon Sep 17 00:00:00 2001 From: Sameer Naik Date: Sat, 7 Nov 2015 11:52:28 +0530 Subject: [PATCH] hub.docker.com now builds images from git tags. --- CI_MIGRATION.md | 30 +++++------ Dockerfile | 2 +- Makefile | 10 ++-- README.md | 76 ++++++++++++++-------------- docker-compose.yml | 6 +-- kubernetes/postgresql-controller.yml | 2 +- 6 files changed, 63 insertions(+), 63 deletions(-) diff --git a/CI_MIGRATION.md b/CI_MIGRATION.md index 10dea76ee..c1a8c2571 100644 --- a/CI_MIGRATION.md +++ b/CI_MIGRATION.md @@ -2,7 +2,7 @@ Since version `8.0.0`, CI is now a part of GitLab. You no longer need to run a separate instance of the CI server. This guide walks you through the procedure of migrating your existing CI data into GitLab. -This guide assumes that you are currently using `quay.io/sameersbn/gitlab` and `quay.io/sameersbn/gitlab-ci` for setting up your GitLab and CI requirements. +This guide assumes that you are currently using `sameersbn/gitlab` and `sameersbn/gitlab-ci` for setting up your GitLab and CI requirements. > **Note:** > @@ -21,18 +21,18 @@ docker rm gitlab-ci gitlab Migration to GitLab `8.0` can only be done from version `7.14.3`. As a result we need to first migrate to the most recent versions of these images. -### Upgrade to `quay.io/sameersbn/gitlab:7.14.3` +### Upgrade to `sameersbn/gitlab:7.14.3` ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:7.14.3 app:init + sameersbn/gitlab:7.14.3 app:init ``` -### Upgrade to `quay.io/sameersbn/gitlab-ci:7.14.3-1` +### Upgrade to `sameersbn/gitlab-ci:7.14.3-1` ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab-ci:7.14.3-1 app:init + sameersbn/gitlab-ci:7.14.3-1 app:init ``` ## Step 3 - Generate Backups @@ -43,7 +43,7 @@ Create backups to ensure that we can rollback in case you face issues during the ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:7.14.3 app:rake gitlab:backup:create + sameersbn/gitlab:7.14.3 app:rake gitlab:backup:create ``` Make a note of the backup archive `xxxxxxxxxx_gitlab_backup.tar` as it is the backup you will have to rollback to in case of errors. @@ -52,7 +52,7 @@ Make a note of the backup archive `xxxxxxxxxx_gitlab_backup.tar` as it is the ba ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab-ci:7.14.3-1 app:rake backup:create + sameersbn/gitlab-ci:7.14.3-1 app:rake backup:create ``` Make a note of the backup archive `xxxxxxxxxx_gitlab_ci_backup.tar.gz` as it is the backup you will have to rollback to in case of errors. @@ -63,11 +63,11 @@ Make a note of the backup archive `xxxxxxxxxx_gitlab_ci_backup.tar.gz` as it is CI `8.x.x` is only meant for the purpose of migrating to GitLab `8.0`. Here we need to upgrade to version `8.x.x` and generate a backup that will be imported into GitLab. -### Upgrade to `quay.io/sameersbn/gitlab-ci:8.0.5` +### Upgrade to `sameersbn/gitlab-ci:8.0.5` ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab-ci:8.0.5 app:init + sameersbn/gitlab-ci:8.0.5 app:init ``` ### Create CI backup @@ -76,7 +76,7 @@ docker run -it --rm [OPTIONS] \ ```bash docker run -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab-ci:8.0.5 app:rake backup:create + sameersbn/gitlab-ci:8.0.5 app:rake backup:create ``` Copy the generated backup archive `xxxxxxxxxx_gitlab_ci_backup.tar` into the `backups/` directory of the GitLab server. @@ -85,20 +85,20 @@ Copy the generated backup archive `xxxxxxxxxx_gitlab_ci_backup.tar` into the `ba cp /backups/xxxxxxxxxx_gitlab_ci_backup.tar /backups/ ``` -We are done with CI. If the rest of the migration goes was planned you will not need to start `quay.io/sameersbn/gitlab-ci` ever again. +We are done with CI. If the rest of the migration goes was planned you will not need to start `sameersbn/gitlab-ci` ever again. ## Step 5 - Upgrade GitLab -Before we can upgrade to `quay.io/sameersbn/gitlab:8.0.5-1`, we need to assign the value of `GITLAB_CI_SECRETS_DB_KEY_BASE` (from CI) to `GITLAB_SECRETS_DB_KEY_BASE` in GitLab's environment. +Before we can upgrade to `sameersbn/gitlab:8.0.5-1`, we need to assign the value of `GITLAB_CI_SECRETS_DB_KEY_BASE` (from CI) to `GITLAB_SECRETS_DB_KEY_BASE` in GitLab's environment. Next you also need to set the environment variable `GITLAB_CI_HOST` to the address of your CI server, eg. `ci.example.com`. This will make sure that your existing runners will be able to communicate to GitLab with the old url. -### Upgrade to `quay.io/sameersbn/gitlab:8.0.5-1` +### Upgrade to `sameersbn/gitlab:8.0.5-1` ```bash docker run -it --rm [OPTIONS] \ --env GITLAB_CI_HOST=ci.example.com --env GITLAB_SECRETS_DB_KEY_BASE=xxxxxx \ - quay.io/sameersbn/gitlab:8.0.5-1 app:init + sameersbn/gitlab:8.0.5-1 app:init ``` ### Migrate CI data @@ -106,7 +106,7 @@ docker run -it --rm [OPTIONS] \ ```bash docker run -it --rm [OPTIONS] \ --env GITLAB_CI_HOST=ci.example.com --env GITLAB_SECRETS_DB_KEY_BASE=xxxxxx \ - quay.io/sameersbn/gitlab:8.0.5-1 app:rake ci:migrate + sameersbn/gitlab:8.0.5-1 app:rake ci:migrate ``` ## Step 6 - Fix DNS and reverse proxy configurations diff --git a/Dockerfile b/Dockerfile index aa596b708..116a58d22 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,4 +1,4 @@ -FROM quay.io/sameersbn/ubuntu:14.04.20151023 +FROM sameersbn/ubuntu:14.04.20151023 MAINTAINER sameer@damagehead.com ENV GITLAB_VERSION=8.1.3 \ diff --git a/Makefile b/Makefile index 936714fcd..23f7daa36 100644 --- a/Makefile +++ b/Makefile @@ -11,26 +11,26 @@ help: @echo " 5. make purge - stop and remove the container" build: - @docker build --tag=quay.io/sameersbn/gitlab . + @docker build --tag=sameersbn/gitlab . release: build - @docker build --tag=quay.io/sameersbn/gitlab:$(shell cat VERSION) . + @docker build --tag=sameersbn/gitlab:$(shell cat VERSION) . quickstart: @echo "Starting postgresql container..." @docker run --name=gitlab-postgresql -d \ --env='DB_NAME=gitlabhq_production' \ --env='DB_USER=gitlab' --env='DB_PASS=password' \ - quay.io/sameersbn/postgresql:latest + sameersbn/postgresql:latest @echo "Starting redis container..." @docker run --name=gitlab-redis -d \ - quay.io/sameersbn/redis:latest + sameersbn/redis:latest @echo "Starting gitlab container..." @docker run --name='gitlab-demo' -d \ --link=gitlab-postgresql:postgresql --link=gitlab-redis:redisio \ --publish=10022:22 --publish=10080:80 \ --env='GITLAB_PORT=10080' --env='GITLAB_SSH_PORT=10022' \ - quay.io/sameersbn/gitlab:latest + sameersbn/gitlab:latest @echo "Please be patient. This could take a while..." @echo "GitLab will be available at http://localhost:10080" @echo "Type 'make logs' for the logs" diff --git a/README.md b/README.md index 81aba2971..93e79e970 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ [![Deploy to Tutum](https://s.tutum.co/deploy-to-tutum.svg)](https://dashboard.tutum.co/stack/deploy/) -# quay.io/sameersbn/gitlab:8.1.3 +# sameersbn/gitlab:8.1.3 - [Introduction](#introduction) - [Version](#version) @@ -113,18 +113,18 @@ Your docker host needs to have 1GB or more of available RAM to run GitLab. Pleas # Installation -Automated builds of the image are available on [Quay.io](https://quay.io/repository/sameersbn/gitlab) and is the recommended method of installation. +Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) and is the recommended method of installation. -> **Note**: Builds are also available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) +> **Note**: Builds are also available on [Quay.io](https://quay.io/repository/sameersbn/gitlab) ```bash -docker pull quay.io/sameersbn/gitlab:8.1.3 +docker pull sameersbn/gitlab:8.1.3 ``` You can also pull the `latest` tag which is built from the repository *HEAD* ```bash -docker pull quay.io/sameersbn/gitlab:latest +docker pull sameersbn/gitlab:latest ``` Alternatively you can build the image locally. @@ -162,7 +162,7 @@ docker run --name gitlab-postgresql -d \ --env 'DB_NAME=gitlabhq_production' \ --env 'DB_USER=gitlab' --env 'DB_PASS=password' \ --volume /srv/docker/gitlab/postgresql:/var/lib/postgresql \ - quay.io/sameersbn/postgresql:9.4-5 + sameersbn/postgresql:9.4-7 ``` Step 2. Launch a redis container @@ -170,7 +170,7 @@ Step 2. Launch a redis container ```bash docker run --name gitlab-redis -d \ --volume /srv/docker/gitlab/redis:/var/lib/redis \ - quay.io/sameersbn/redis:latest + sameersbn/redis:latest ``` Step 3. Launch the gitlab container @@ -182,7 +182,7 @@ docker run --name gitlab -d \ --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' \ --env 'GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alpha-numeric-string' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` *Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options* @@ -218,7 +218,7 @@ Volumes can be mounted in docker by specifying the `-v` option in the docker run ```bash docker run --name gitlab -d \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` ## Database @@ -249,7 +249,7 @@ docker run --name gitlab -d \ --env 'DB_NAME=gitlabhq_production' \ --env 'DB_USER=gitlab' --env 'DB_PASS=password' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` #### Linking to PostgreSQL Container @@ -263,7 +263,7 @@ To illustrate linking with a postgresql container, we will use the [sameersbn/po First, lets pull the postgresql image from the docker index. ```bash -docker pull quay.io/sameersbn/postgresql:9.4-5 +docker pull sameersbn/postgresql:9.4-7 ``` For data persistence lets create a store for the postgresql and start the container. @@ -282,7 +282,7 @@ docker run --name gitlab-postgresql -d \ --env 'DB_NAME=gitlabhq_production' \ --env 'DB_USER=gitlab' --env 'DB_PASS=password' \ --volume /srv/docker/gitlab/postgresql:/var/lib/postgresql \ - quay.io/sameersbn/postgresql:9.4-5 + sameersbn/postgresql:9.4-7 ``` 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. @@ -292,7 +292,7 @@ We are now ready to start the GitLab application. ```bash docker run --name gitlab -d --link gitlab-postgresql:postgresql \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` 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: @@ -315,7 +315,7 @@ Assuming that your mysql data is available at `/srv/docker/gitlab/mysql` ```bash docker run --name gitlab-mysql -d \ --volume /srv/docker/gitlab/mysql:/var/lib/mysql \ - quay.io/sameersbn/mysql:latest + sameersbn/mysql:latest ``` This will start a mysql container with your existing mysql data. Now login to the mysql container and create a user for the existing `gitlabhq_production` database. @@ -345,7 +345,7 @@ 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 \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` #### Linking to MySQL Container @@ -359,7 +359,7 @@ To illustrate linking with a mysql container, we will use the [sameersbn/mysql]( First, lets pull the mysql image from the docker index. ```bash -docker pull quay.io/sameersbn/mysql:latest +docker pull sameersbn/mysql:latest ``` For data persistence lets create a store for the mysql and start the container. @@ -378,7 +378,7 @@ docker run --name gitlab-mysql -d \ --env 'DB_NAME=gitlabhq_production' \ --env 'DB_USER=gitlab' --env 'DB_PASS=password' \ --volume /srv/docker/gitlab/mysql:/var/lib/mysql \ - quay.io/sameersbn/mysql:latest + sameersbn/mysql:latest ``` The above command will create a database named `gitlabhq_production` and also create a user named `gitlab` with the password `password` with full/remote access to the `gitlabhq_production` database. @@ -388,7 +388,7 @@ We are now ready to start the GitLab application. ```bash docker run --name gitlab -d --link gitlab-mysql:mysql \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the mysql container as they are specified in the `docker run` command for the mysql container. This is made possible using the magic of docker links and works with the following images: @@ -415,7 +415,7 @@ The image can be configured to use an external redis server. The configuration s ```bash docker run --name gitlab -it --rm \ --env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` ### Linking to Redis Container @@ -427,7 +427,7 @@ To illustrate linking with a redis container, we will use the [sameersbn/redis]( First, lets pull the redis image from the docker index. ```bash -docker pull quay.io/sameersbn/redis:latest +docker pull sameersbn/redis:latest ``` Lets start the redis container @@ -435,14 +435,14 @@ Lets start the redis container ```bash docker run --name gitlab-redis -d \ --volume /srv/docker/gitlab/redis:/var/lib/redis \ - quay.io/sameersbn/redis:latest + sameersbn/redis:latest ``` We are now ready to start the GitLab application. ```bash docker run --name gitlab -d --link gitlab-redis:redisio \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` ### Mail @@ -455,7 +455,7 @@ If you are using Gmail then all you need to do is: docker run --name gitlab -d \ --env 'SMTP_USER=USER@gmail.com' --env 'SMTP_PASS=PASSWORD' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.0.0 + sameersbn/gitlab:8.0.0 ``` Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified. @@ -472,7 +472,7 @@ If you are using Gmail then all you need to do is: docker run --name gitlab -d \ --env 'IMAP_USER=USER@gmail.com' --env 'IMAP_PASS=PASSWORD' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified. @@ -549,7 +549,7 @@ docker run --name gitlab -d \ --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 \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` 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. @@ -565,7 +565,7 @@ docker run --name gitlab -d \ --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \ --env 'GITLAB_HTTPS_HSTS_MAXAGE=2592000' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` If you want to completely disable HSTS set `GITLAB_HTTPS_HSTS_ENABLED` to `false`. @@ -588,7 +588,7 @@ docker run --name gitlab -d \ --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 \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` Again, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates. @@ -636,7 +636,7 @@ Let's assume we want to deploy our application to '/git'. GitLab needs to know t docker run --name gitlab -it --rm \ --env 'GITLAB_RELATIVE_URL_ROOT=/git' \ --volume /srv/docker/gitlab/gitlab:/home/git/data \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`. @@ -730,14 +730,14 @@ Also the container processes seem to be executed as the host's user/group `1000` ```bash docker run --name gitlab -it --rm [options] \ --env "USERMAP_UID=$(id -u git)" --env "USERMAP_GID=$(id -g git)" \ - quay.io/sameersbn/gitlab:8.1.3 + sameersbn/gitlab:8.1.3 ``` When changing this mapping, all files and directories in the mounted data volume `/home/git/data` have to be re-owned by the new ids. This can be achieved automatically using the following command: ```bash docker run --name gitlab -d [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:sanitize + sameersbn/gitlab:8.1.3 app:sanitize ``` ### Piwik @@ -906,7 +906,7 @@ Execute the rake task to create a backup. ```bash docker run --name gitlab -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:rake gitlab:backup:create + sameersbn/gitlab:8.1.3 app:rake gitlab:backup:create ``` A backup will be created in the backups folder of the [Data Store](#data-store). You can change the location of the backups using the `GITLAB_BACKUP_DIR` configuration parameter. @@ -927,7 +927,7 @@ Execute the rake task to restore a backup. Make sure you run the container in in ```bash docker run --name gitlab -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:rake gitlab:backup:restore + sameersbn/gitlab:8.1.3 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. @@ -936,7 +936,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the ```bash docker run --name gitlab -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:rake gitlab:backup:restore BACKUP=1417624827 + sameersbn/gitlab:8.1.3 app:rake gitlab:backup:restore BACKUP=1417624827 ``` ## Automated Backups @@ -961,7 +961,7 @@ The `app:rake` command allows you to run gitlab rake tasks. To run a rake task s ```bash docker run --name gitlab -d [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:rake gitlab:env:info + sameersbn/gitlab:8.1.3 app:rake gitlab:env:info ``` You can also use `docker exec` to run raketasks on running gitlab instance. For example, @@ -974,7 +974,7 @@ Similarly, to import bare repositories into GitLab project instance ```bash docker run --name gitlab -d [OPTIONS] \ - quay.io/sameersbn/gitlab:8.1.3 app:rake gitlab:import:repos + sameersbn/gitlab:8.1.3 app:rake gitlab:import:repos ``` Or @@ -996,7 +996,7 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure - **Step 1**: Update the docker image. ```bash -docker pull quay.io/sameersbn/gitlab:8.1.3 +docker pull sameersbn/gitlab:8.1.3 ``` - **Step 2**: Stop and remove the currently running image @@ -1010,7 +1010,7 @@ docker rm gitlab ```bash docker run --name gitlab -it --rm [OPTIONS] \ - quay.io/sameersbn/gitlab:x.x.x app:rake gitlab:backup:create + sameersbn/gitlab:x.x.x app:rake gitlab:backup:create ``` Replace `x.x.x` with the version you are upgrading from. For example, if you are upgrading from version `6.0.0`, set `x.x.x` to `6.0.0` @@ -1020,7 +1020,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are > **Note**: Since GitLab `8.0.0` you need to provide the `GITLAB_SECRETS_DB_KEY_BASE` parameter while starting the image. ```bash -docker run --name gitlab -d [OPTIONS] quay.io/sameersbn/gitlab:8.1.3 +docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:8.1.3 ``` ## Shell Access diff --git a/docker-compose.yml b/docker-compose.yml index 98c8aa690..205ec708c 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -1,5 +1,5 @@ postgresql: - image: quay.io/sameersbn/postgresql:9.4-5 + image: sameersbn/postgresql:9.4-7 environment: - DB_USER=gitlab - DB_PASS=password @@ -7,7 +7,7 @@ postgresql: volumes: - /srv/docker/gitlab/postgresql:/var/lib/postgresql gitlab: - image: quay.io/sameersbn/gitlab:8.1.3 + image: sameersbn/gitlab:8.1.3 links: - redis:redisio - postgresql:postgresql @@ -54,6 +54,6 @@ gitlab: volumes: - /srv/docker/gitlab/gitlab:/home/git/data redis: - image: quay.io/sameersbn/redis:latest + image: sameersbn/redis:latest volumes: - /srv/docker/gitlab/redis:/var/lib/redis diff --git a/kubernetes/postgresql-controller.yml b/kubernetes/postgresql-controller.yml index dcb3453f7..ce5d46232 100644 --- a/kubernetes/postgresql-controller.yml +++ b/kubernetes/postgresql-controller.yml @@ -15,7 +15,7 @@ spec: spec: containers: - name: postgresql - image: quay.io/sameersbn/postgresql:9.4-5 + image: sameersbn/postgresql:9.4-7 env: - name: DB_USER value: gitlab