Upgrade GitLab CE to 18.1.0

This commit is contained in:
Steven Achilles
2025-06-19 20:02:01 +02:00
parent 04bfca3805
commit 82ba5b8c35
11 changed files with 49 additions and 43 deletions

View File

@ -3,6 +3,12 @@
This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://
gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in GitLab.
## 18.1.0
- gitlab: upgrade CE to v18.1.0
- gitaly: upgrade to v18.1.0
- gitlab-pages: upgrade to v18.1.0
## 18.0.2
- gitlab: upgrade CE to v18.0.2

View File

@ -1,6 +1,6 @@
FROM ubuntu:noble-20250529
ARG VERSION=18.0.2
ARG VERSION=18.1.0
ENV GITLAB_VERSION=${VERSION} \
RUBY_VERSION=3.2.8 \
@ -8,8 +8,8 @@ ENV GITLAB_VERSION=${VERSION} \
RUBYGEMS_VERSION=3.6.9 \
GOLANG_VERSION=1.24.4 \
GITLAB_SHELL_VERSION=14.42.0 \
GITLAB_PAGES_VERSION=18.0.2 \
GITALY_SERVER_VERSION=18.0.2 \
GITLAB_PAGES_VERSION=18.1.0 \
GITALY_SERVER_VERSION=18.1.0 \
GITLAB_USER="git" \
GITLAB_HOME="/home/git" \
GITLAB_LOG_DIR="/var/log/gitlab" \

View File

@ -1,4 +1,4 @@
# sameersbn/gitlab:18.0.2
# sameersbn/gitlab:18.1.0
[![CircleCI](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master.svg?style=svg)](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master)
@ -128,7 +128,7 @@ Your docker host needs to have 1GB or more of available RAM to run GitLab. Pleas
Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) and is the recommended method of installation.
```bash
docker pull sameersbn/gitlab:18.0.2
docker pull sameersbn/gitlab:18.1.0
```
You can also pull the `latest` tag which is built from the repository *HEAD*
@ -210,7 +210,7 @@ docker run --name gitlab -d \
--env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY=["long-and-random-alpha-numeric-string"]' \
--env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT=long-and-random-alpha-numeric-string' \
--volume /srv/docker/gitlab/gitlab:/home/git/data \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@ -245,7 +245,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
### Database
@ -286,7 +286,7 @@ Please note furthermore, that only compatible versions of the `postgresql-client
- GitLab CE version 13.7.0 and later requires PostgreSQL version 12.x.
- GitLab CE version 16.0.0 and later requires PostgreSQL version 13.x.
- GitLab CE version 17.0.0 and later requires PostgreSQL version 14.x.
- GitLab CE version 18.0.2 and later requires PostgreSQL version 16.x.
- GitLab CE version 18.1.0 and later requires PostgreSQL version 16.x.
##### External PostgreSQL Server
@ -310,7 +310,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
##### Linking to PostgreSQL Container
@ -354,7 +354,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
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:
@ -392,7 +392,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' \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
#### Linking to Redis Container
@ -419,7 +419,7 @@ We are now ready to start the GitLab application.
```bash
docker run --name gitlab -d --link gitlab-redis:redisio \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
#### Mail
@ -432,7 +432,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.
@ -452,7 +452,7 @@ docker run --name gitlab -d \
--env 'IMAP_USER=USER@gmail.com' --env 'IMAP_PASS=PASSWORD' \
--env 'GITLAB_INCOMING_EMAIL_ADDRESS=USER+%{key}@gmail.com' \
--volume /srv/docker/gitlab/gitlab:/home/git/data \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
@ -536,7 +536,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
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.
@ -552,7 +552,7 @@ docker run --name gitlab -d \
--env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
--env 'NGINX_HSTS_MAXAGE=2592000' \
--volume /srv/docker/gitlab/gitlab:/home/git/data \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@ -575,7 +575,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
Again, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates.
@ -623,7 +623,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 \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`.
@ -850,14 +850,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)" \
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
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] \
sameersbn/gitlab:18.0.2 app:sanitize
sameersbn/gitlab:18.1.0 app:sanitize
```
#### Piwik
@ -2612,7 +2612,7 @@ Execute the rake task to create a backup.
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:create
sameersbn/gitlab:18.1.0 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.
@ -2647,14 +2647,14 @@ you need to prepare the database:
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake db:setup
sameersbn/gitlab:18.1.0 app:rake db:setup
```
Execute the rake task to restore a backup. Make sure you run the container in interactive mode `-it`.
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:restore
sameersbn/gitlab:18.1.0 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.
@ -2663,7 +2663,7 @@ To avoid user interaction in the restore operation, specify the timestamp, date
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
sameersbn/gitlab:18.1.0 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
```
When using `docker-compose` you may use the following command to execute the restore.
@ -2712,7 +2712,7 @@ The `app:rake` command allows you to run gitlab rake tasks. To run a rake task s
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:env:info
sameersbn/gitlab:18.1.0 app:rake gitlab:env:info
```
You can also use `docker exec` to run rake tasks on running gitlab instance. For example,
@ -2725,7 +2725,7 @@ Similarly, to import bare repositories into GitLab project instance
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:import:repos
sameersbn/gitlab:18.1.0 app:rake gitlab:import:repos
```
Or
@ -2756,7 +2756,7 @@ Copy all the **bare** git repositories to the `repositories/` directory of the [
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:import:repos
sameersbn/gitlab:18.1.0 app:rake gitlab:import:repos
```
Watch the logs and your repositories should be available into your new gitlab container.
@ -2787,12 +2787,12 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
> **Note**
>
> Upgrading to `sameersbn/gitlab:18.0.2` from `sameersbn/gitlab:7.x.x` can cause issues. It is therefore required that you first upgrade to `sameersbn/gitlab:8.0.5-1` before upgrading to `sameersbn/gitlab:8.1.0` or higher.
> Upgrading to `sameersbn/gitlab:18.1.0` from `sameersbn/gitlab:7.x.x` can cause issues. It is therefore required that you first upgrade to `sameersbn/gitlab:8.0.5-1` before upgrading to `sameersbn/gitlab:8.1.0` or higher.
- **Step 1**: Update the docker image.
```bash
docker pull sameersbn/gitlab:18.0.2
docker pull sameersbn/gitlab:18.1.0
```
- **Step 2**: Stop and remove the currently running image
@ -2822,7 +2822,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
> **Note**: Since Gitlab 17.8 you need to provide `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY`,`GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY` and `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT`. If not provided, these keys will be generated by gitlab. The image can be started without setting these parameters, **but you will lose the settings when you shutting down the container without taking a backup of `secrets.yml` and settings stored securely (such as the Dependency Proxy) will be unusable and unrecoverable.**
```bash
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:18.0.2
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:18.1.0
```
### Shell Access
@ -2858,7 +2858,7 @@ You can also set your `docker-compose.yml` [healthcheck](https://docs.docker.com
```yml
services:
gitlab:
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
healthcheck:
test: ["CMD", "/usr/local/sbin/healthcheck"]
interval: 1m

View File

@ -1 +1 @@
18.0.2
18.1.0

View File

@ -20,7 +20,7 @@ services:
gitlab:
restart: always
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
depends_on:
- redis
- postgresql

View File

@ -62,7 +62,7 @@ services:
- traefik-public
gitlab:
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
depends_on:
- redis
- postgresql

View File

@ -21,7 +21,7 @@ services:
gitlab:
restart: always
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
depends_on:
- redis
- postgresql

View File

@ -291,7 +291,7 @@ Execute the rake task with a removeable container.
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:create
sameersbn/gitlab:18.1.0 app:rake gitlab:backup:create
```
### Restoring Backups
@ -308,7 +308,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] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:restore
sameersbn/gitlab:18.1.0 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.
@ -317,7 +317,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the
```bash
docker run --name gitlab -it --rm [OPTIONS] \
sameersbn/gitlab:18.0.2 app:rake gitlab:backup:restore BACKUP=1417624827
sameersbn/gitlab:18.1.0 app:rake gitlab:backup:restore BACKUP=1417624827
```
## Upgrading from an existing GitLab installation
@ -327,7 +327,7 @@ If you want enable this feature for an existing instance of GitLab you need to d
- **Step 1**: Update the docker image.
```bash
docker pull sameersbn/gitlab:18.0.2
docker pull sameersbn/gitlab:18.1.0
```
- **Step 2**: Stop and remove the currently running image
@ -381,7 +381,7 @@ docker run --name gitlab -d [PREVIOUS_OPTIONS] \
--env 'GITLAB_REGISTRY_CERT_PATH=/certs/registry-auth.crt' \
--env 'GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key' \
--link registry:registry
sameersbn/gitlab:18.0.2
sameersbn/gitlab:18.1.0
```
[storage-config]: https://docs.docker.com/registry/configuration/#storage

View File

@ -20,7 +20,7 @@ services:
gitlab:
restart: always
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
depends_on:
- redis
- postgresql

View File

@ -20,7 +20,7 @@ services:
gitlab:
restart: always
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
volumes:
- gitlab-data:/home/git/data:Z
- gitlab-logs:/var/log/gitlab

View File

@ -14,7 +14,7 @@ spec:
spec:
containers:
- name: gitlab
image: sameersbn/gitlab:18.0.2
image: sameersbn/gitlab:18.1.0
env:
- name: TZ
value: Asia/Kolkata