Skip to content

Commit 5cda38a

Browse files
sachillessachilles
authored
Merge pull request #3305 from vunguyen-it/upgrade-to-19.4.1
Upgrade to GitLab CE 19.4.1 (Critical Patch)
2 parents f86ceaa + cf9aa31 commit 5cda38a

11 files changed

Lines changed: 46 additions & 40 deletions

‎Changelog.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,12 @@
33
This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://
44
gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in GitLab.
55

6+
## 19.4.1
7+
8+
- gitlab: upgrade CE to v19.4.1
9+
- gitaly: upgrade to v19.4.1
10+
- gitlab-pages: upgrade to v19.4.1
11+
612
## 19.4.0
713

814
- gitlab: upgrade CE to v19.4.0

‎Dockerfile‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
FROM ubuntu:noble-20260911
22

3-
ARG VERSION=19.4.0
3+
ARG VERSION=19.4.1
44

55
ENV GITLAB_VERSION=${VERSION} \
66
RUBY_VERSION=3.3.12 \
77
RUBY_SOURCE_SHA256SUM="b06d63beae271933033e27f0a389bc582a009e7845357d44365c39de525a051b" \
88
RUBYGEMS_VERSION=4.0.21 \
99
GOLANG_VERSION=1.27.1 \
1010
GITLAB_SHELL_VERSION=14.57.3 \
11-
GITLAB_PAGES_VERSION=19.4.0 \
12-
GITALY_SERVER_VERSION=19.4.0 \
11+
GITLAB_PAGES_VERSION=19.4.1 \
12+
GITALY_SERVER_VERSION=19.4.1 \
1313
GITLAB_USER="git" \
1414
GITLAB_HOME="/home/git" \
1515
GITLAB_LOG_DIR="/var/log/gitlab" \

‎README.md‎

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# sameersbn/gitlab:19.4.0
1+
# sameersbn/gitlab:19.4.1
22

33
[![CircleCI](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master.svg?style=svg)](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master)
44

@@ -129,7 +129,7 @@ Your docker host needs to have 1GB or more of available RAM to run GitLab. Pleas
129129
Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) and is the recommended method of installation.
130130

131131
```bash
132-
docker pull sameersbn/gitlab:19.4.0
132+
docker pull sameersbn/gitlab:19.4.1
133133
```
134134

135135
You can also pull the `latest` tag which is built from the repository *HEAD*
@@ -212,7 +212,7 @@ docker run --name gitlab -d \
212212
--env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY=["long-and-random-alpha-numeric-string"]' \
213213
--env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT=long-and-random-alpha-numeric-string' \
214214
--volume /srv/docker/gitlab/gitlab:/home/git/data \
215-
sameersbn/gitlab:19.4.0
215+
sameersbn/gitlab:19.4.1
216216
```
217217

218218
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@@ -247,7 +247,7 @@ Volumes can be mounted in docker by specifying the `-v` option in the docker run
247247
```bash
248248
docker run --name gitlab -d \
249249
--volume /srv/docker/gitlab/gitlab:/home/git/data \
250-
sameersbn/gitlab:19.4.0
250+
sameersbn/gitlab:19.4.1
251251
```
252252

253253
### Database
@@ -310,7 +310,7 @@ docker run --name gitlab -d \
310310
--env 'DB_NAME=gitlabhq_production' \
311311
--env 'DB_USER=gitlab' --env 'DB_PASS=password' \
312312
--volume /srv/docker/gitlab/gitlab:/home/git/data \
313-
sameersbn/gitlab:19.4.0
313+
sameersbn/gitlab:19.4.1
314314
```
315315

316316
##### Linking to PostgreSQL Container
@@ -355,7 +355,7 @@ We are now ready to start the GitLab application.
355355
```bash
356356
docker run --name gitlab -d --link gitlab-postgresql:postgresql \
357357
--volume /srv/docker/gitlab/gitlab:/home/git/data \
358-
sameersbn/gitlab:19.4.0
358+
sameersbn/gitlab:19.4.1
359359
```
360360

361361
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:
@@ -393,7 +393,7 @@ The image can be configured to use an external redis server. The configuration s
393393
```bash
394394
docker run --name gitlab -it --rm \
395395
--env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \
396-
sameersbn/gitlab:19.4.0
396+
sameersbn/gitlab:19.4.1
397397
```
398398

399399
#### Linking to Redis Container
@@ -420,7 +420,7 @@ We are now ready to start the GitLab application.
420420

421421
```bash
422422
docker run --name gitlab -d --link gitlab-redis:redisio \
423-
sameersbn/gitlab:19.4.0
423+
sameersbn/gitlab:19.4.1
424424
```
425425

426426
#### Mail
@@ -433,7 +433,7 @@ If you are using Gmail then all you need to do is:
433433
docker run --name gitlab -d \
434434
--env 'SMTP_USER=USER@gmail.com' --env 'SMTP_PASS=PASSWORD' \
435435
--volume /srv/docker/gitlab/gitlab:/home/git/data \
436-
sameersbn/gitlab:19.4.0
436+
sameersbn/gitlab:19.4.1
437437
```
438438

439439
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.
@@ -473,7 +473,7 @@ docker run --name gitlab -d \
473473
--env 'IMAP_USER=USER@gmail.com' --env 'IMAP_PASS=PASSWORD' \
474474
--env 'GITLAB_INCOMING_EMAIL_ADDRESS=USER+%{key}@gmail.com' \
475475
--volume /srv/docker/gitlab/gitlab:/home/git/data \
476-
sameersbn/gitlab:19.4.0
476+
sameersbn/gitlab:19.4.1
477477
```
478478

479479
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
@@ -557,7 +557,7 @@ docker run --name gitlab -d \
557557
--env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=10443' \
558558
--env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
559559
--volume /srv/docker/gitlab/gitlab:/home/git/data \
560-
sameersbn/gitlab:19.4.0
560+
sameersbn/gitlab:19.4.1
561561
```
562562

563563
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.
@@ -573,7 +573,7 @@ docker run --name gitlab -d \
573573
--env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
574574
--env 'NGINX_HSTS_MAXAGE=2592000' \
575575
--volume /srv/docker/gitlab/gitlab:/home/git/data \
576-
sameersbn/gitlab:19.4.0
576+
sameersbn/gitlab:19.4.1
577577
```
578578

579579
If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@@ -596,7 +596,7 @@ docker run --name gitlab -d \
596596
--env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=443' \
597597
--env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
598598
--volume /srv/docker/gitlab/gitlab:/home/git/data \
599-
sameersbn/gitlab:19.4.0
599+
sameersbn/gitlab:19.4.1
600600
```
601601

602602
Again, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates.
@@ -644,7 +644,7 @@ Let's assume we want to deploy our application to '/git'. GitLab needs to know t
644644
docker run --name gitlab -it --rm \
645645
--env 'GITLAB_RELATIVE_URL_ROOT=/git' \
646646
--volume /srv/docker/gitlab/gitlab:/home/git/data \
647-
sameersbn/gitlab:19.4.0
647+
sameersbn/gitlab:19.4.1
648648
```
649649

650650
GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`.
@@ -871,14 +871,14 @@ Also the container processes seem to be executed as the host's user/group `1000`
871871
```bash
872872
docker run --name gitlab -it --rm [options] \
873873
--env "USERMAP_UID=$(id -u git)" --env "USERMAP_GID=$(id -g git)" \
874-
sameersbn/gitlab:19.4.0
874+
sameersbn/gitlab:19.4.1
875875
```
876876

877877
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:
878878

879879
```bash
880880
docker run --name gitlab -d [OPTIONS] \
881-
sameersbn/gitlab:19.4.0 app:sanitize
881+
sameersbn/gitlab:19.4.1 app:sanitize
882882
```
883883

884884
#### Piwik
@@ -2677,7 +2677,7 @@ Execute the rake task to create a backup.
26772677

26782678
```bash
26792679
docker run --name gitlab -it --rm [OPTIONS] \
2680-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:create
2680+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:create
26812681
```
26822682

26832683
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.
@@ -2712,14 +2712,14 @@ you need to prepare the database:
27122712

27132713
```bash
27142714
docker run --name gitlab -it --rm [OPTIONS] \
2715-
sameersbn/gitlab:19.4.0 app:rake db:setup
2715+
sameersbn/gitlab:19.4.1 app:rake db:setup
27162716
```
27172717

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

27202720
```bash
27212721
docker run --name gitlab -it --rm [OPTIONS] \
2722-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:restore
2722+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:restore
27232723
```
27242724

27252725
The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.
@@ -2728,7 +2728,7 @@ To avoid user interaction in the restore operation, specify the timestamp, date
27282728

27292729
```bash
27302730
docker run --name gitlab -it --rm [OPTIONS] \
2731-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
2731+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
27322732
```
27332733

27342734
When using `docker-compose` you may use the following command to execute the restore.
@@ -2777,7 +2777,7 @@ The `app:rake` command allows you to run gitlab rake tasks. To run a rake task s
27772777

27782778
```bash
27792779
docker run --name gitlab -it --rm [OPTIONS] \
2780-
sameersbn/gitlab:19.4.0 app:rake gitlab:env:info
2780+
sameersbn/gitlab:19.4.1 app:rake gitlab:env:info
27812781
```
27822782

27832783
You can also use `docker exec` to run rake tasks on running gitlab instance. For example,
@@ -2806,7 +2806,7 @@ GitLab 16.0 removed the Rake task for importing bare repositories. To import a p
28062806

28072807
```bash
28082808
docker run --name gitlab -it --rm [OPTIONS] \
2809-
sameersbn/gitlab:19.4.0 app:rake \
2809+
sameersbn/gitlab:19.4.1 app:rake \
28102810
"gitlab:import_export:import[root,group/subgroup,project,/home/git/data/project.tar.gz]"
28112811
```
28122812

@@ -2862,7 +2862,7 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
28622862
- **Step 1**: Update the docker image.
28632863

28642864
```bash
2865-
docker pull sameersbn/gitlab:19.4.0
2865+
docker pull sameersbn/gitlab:19.4.1
28662866
```
28672867

28682868
- **Step 2**: Stop and remove the currently running image
@@ -2892,7 +2892,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
28922892
> **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.**
28932893

28942894
```bash
2895-
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:19.4.0
2895+
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:19.4.1
28962896
```
28972897

28982898
### Shell Access
@@ -2928,7 +2928,7 @@ You can also set your `docker-compose.yml` [healthcheck](https://docs.docker.com
29282928
```yml
29292929
services:
29302930
gitlab:
2931-
image: sameersbn/gitlab:19.4.0
2931+
image: sameersbn/gitlab:19.4.1
29322932
healthcheck:
29332933
test: ["CMD", "/usr/local/sbin/healthcheck"]
29342934
interval: 1m

‎VERSION‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
19.4.0
1+
19.4.1

‎contrib/docker-swarm/docker-compose.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ services:
2222

2323
gitlab:
2424
restart: always
25-
image: sameersbn/gitlab:19.4.0
25+
image: sameersbn/gitlab:19.4.1
2626
depends_on:
2727
- redis
2828
- postgresql

‎docker-compose.swarm.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ services:
6363
- traefik-public
6464

6565
gitlab:
66-
image: sameersbn/gitlab:19.4.0
66+
image: sameersbn/gitlab:19.4.1
6767
depends_on:
6868
- redis
6969
- postgresql

‎docker-compose.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ services:
2222

2323
gitlab:
2424
restart: always
25-
image: sameersbn/gitlab:19.4.0
25+
image: sameersbn/gitlab:19.4.1
2626
depends_on:
2727
- redis
2828
- postgresql

‎docs/container_registry.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ Execute the rake task with a removeable container.
298298

299299
```bash
300300
docker run --name gitlab -it --rm [OPTIONS] \
301-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:create
301+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:create
302302
```
303303

304304
### Restoring Backups
@@ -315,7 +315,7 @@ Execute the rake task to restore a backup. Make sure you run the container in in
315315

316316
```bash
317317
docker run --name gitlab -it --rm [OPTIONS] \
318-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:restore
318+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:restore
319319
```
320320

321321
The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.
@@ -324,7 +324,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the
324324

325325
```bash
326326
docker run --name gitlab -it --rm [OPTIONS] \
327-
sameersbn/gitlab:19.4.0 app:rake gitlab:backup:restore BACKUP=1417624827
327+
sameersbn/gitlab:19.4.1 app:rake gitlab:backup:restore BACKUP=1417624827
328328
```
329329

330330
## Upgrading from an existing GitLab installation
@@ -334,7 +334,7 @@ If you want enable this feature for an existing instance of GitLab you need to d
334334
- **Step 1**: Update the docker image.
335335

336336
```bash
337-
docker pull sameersbn/gitlab:19.4.0
337+
docker pull sameersbn/gitlab:19.4.1
338338
```
339339

340340
- **Step 2**: Stop and remove the currently running image
@@ -388,7 +388,7 @@ docker run --name gitlab -d [PREVIOUS_OPTIONS] \
388388
--env 'GITLAB_REGISTRY_CERT_PATH=/certs/registry-auth.crt' \
389389
--env 'GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key' \
390390
--link registry:registry
391-
sameersbn/gitlab:19.4.0
391+
sameersbn/gitlab:19.4.1
392392
```
393393

394394
[storage-config]: https://docs.docker.com/registry/configuration/#storage

‎docs/docker-compose-keycloak.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ services:
2222

2323
gitlab:
2424
restart: always
25-
image: sameersbn/gitlab:19.4.0
25+
image: sameersbn/gitlab:19.4.1
2626
depends_on:
2727
- redis
2828
- postgresql

‎docs/docker-compose-registry.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ services:
2121

2222
gitlab:
2323
restart: always
24-
image: sameersbn/gitlab:19.4.0
24+
image: sameersbn/gitlab:19.4.1
2525
volumes:
2626
- gitlab-data:/home/git/data:Z
2727
- gitlab-logs:/var/log/gitlab

0 commit comments

Comments
 (0)