You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+27-27
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
[](http://microbadger.com/images/sameersbn/gitlab"Get your own image badge on microbadger.com")
2
2
3
-
# sameersbn/gitlab:14.0.3
3
+
# sameersbn/gitlab:14.0.5
4
4
5
5
-[Introduction](#introduction)
6
6
-[Changelog](Changelog.md)
@@ -125,7 +125,7 @@ Your docker host needs to have 1GB or more of available RAM to run GitLab. Pleas
125
125
Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) and is the recommended method of installation.
126
126
127
127
```bash
128
-
docker pull sameersbn/gitlab:14.0.3
128
+
docker pull sameersbn/gitlab:14.0.5
129
129
```
130
130
131
131
You can also pull the `latest` tag which is built from the repository *HEAD*
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@@ -229,7 +229,7 @@ Volumes can be mounted in docker by specifying the `-v` option in the docker run
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:
@@ -347,7 +347,7 @@ The image can be configured to use an external redis server. The configuration s
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
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.
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:
759
759
760
760
```bash
761
761
docker run --name gitlab -d [OPTIONS] \
762
-
sameersbn/gitlab:14.0.3 app:sanitize
762
+
sameersbn/gitlab:14.0.5 app:sanitize
763
763
```
764
764
765
765
### Piwik
@@ -1172,7 +1172,7 @@ Execute the rake task to create a backup.
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.
@@ -1207,14 +1207,14 @@ you need to prepare the database:
1207
1207
1208
1208
```bash
1209
1209
docker run --name gitlab -it --rm [OPTIONS] \
1210
-
sameersbn/gitlab:14.0.3 app:rake db:setup
1210
+
sameersbn/gitlab:14.0.5 app:rake db:setup
1211
1211
```
1212
1212
1213
1213
Execute the rake task to restore a backup. Make sure you run the container in interactive mode `-it`.
Watch the logs and your repositories should be available into your new gitlab container.
@@ -1341,12 +1341,12 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
1341
1341
1342
1342
> **Note**
1343
1343
>
1344
-
> Upgrading to `sameersbn/gitlab:14.0.3` 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.
1344
+
> Upgrading to `sameersbn/gitlab:14.0.5` 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.
1345
1345
1346
1346
-**Step 1**: Update the docker image.
1347
1347
1348
1348
```bash
1349
-
docker pull sameersbn/gitlab:14.0.3
1349
+
docker pull sameersbn/gitlab:14.0.5
1350
1350
```
1351
1351
1352
1352
-**Step 2**: Stop and remove the currently running image
@@ -1372,7 +1372,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
1372
1372
> **Note**: Since GitLab `8.11.0` you need to provide the `GITLAB_SECRETS_SECRET_KEY_BASE` and `GITLAB_SECRETS_OTP_KEY_BASE` parameters while starting the image. These should initially both have the same value as the contents of the `/home/git/data/.secret` file. See [Available Configuration Parameters](#available-configuration-parameters) for more information on these parameters.
1373
1373
1374
1374
```bash
1375
-
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:14.0.3
1375
+
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:14.0.5
0 commit comments