mirror of
https://github.com/sameersbn/docker-gitlab.git
synced 2026-01-18 13:58:25 +00:00
release 8.5.8
This commit is contained in:
Sameer Naik
parent
6258b4af29
commit
e85d6febeb
@ -2,7 +2,7 @@
|
||||
|
||||
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-ce/blob/master/CHANGELOG) for the list of changes in GitLab.
|
||||
|
||||
**latest**
|
||||
**8.5.8**
|
||||
- gitlab: upgrade to CE v8.5.8
|
||||
|
||||
**8.5.7**
|
||||
|
||||
52
README.md
52
README.md
@ -2,7 +2,7 @@
|
||||
|
||||
[](https://dashboard.tutum.co/stack/deploy/)
|
||||
|
||||
# sameersbn/gitlab:8.5.7
|
||||
# sameersbn/gitlab:8.5.8
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Changelog](Changelog.md)
|
||||
@ -111,7 +111,7 @@ Automated builds of the image are available on [Dockerhub](https://hub.docker.co
|
||||
> **Note**: Builds are also available on [Quay.io](https://quay.io/repository/sameersbn/gitlab)
|
||||
|
||||
```bash
|
||||
docker pull sameersbn/gitlab:8.5.7
|
||||
docker pull sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
You can also pull the `latest` tag which is built from the repository *HEAD*
|
||||
@ -173,7 +173,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 \
|
||||
sameersbn/gitlab:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
|
||||
@ -211,7 +211,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
## Database
|
||||
@ -242,7 +242,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
#### Linking to PostgreSQL Container
|
||||
@ -285,7 +285,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
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:
|
||||
@ -339,7 +339,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
#### Linking to MySQL Container
|
||||
@ -382,7 +382,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 \
|
||||
sameersbn/gitlab:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
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:
|
||||
@ -409,7 +409,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
### Linking to Redis Container
|
||||
@ -436,7 +436,7 @@ We are now ready to start the GitLab application.
|
||||
|
||||
```bash
|
||||
docker run --name gitlab -d --link gitlab-redis:redisio \
|
||||
sameersbn/gitlab:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
### Mail
|
||||
@ -466,7 +466,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 \
|
||||
sameersbn/gitlab:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
|
||||
@ -543,7 +543,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
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.
|
||||
@ -559,7 +559,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
|
||||
@ -582,7 +582,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
Again, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates.
|
||||
@ -630,7 +630,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`.
|
||||
@ -740,14 +740,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:8.5.7
|
||||
sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
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:8.5.7 app:sanitize
|
||||
sameersbn/gitlab:8.5.8 app:sanitize
|
||||
```
|
||||
|
||||
### Piwik
|
||||
@ -944,7 +944,7 @@ Execute the rake task to create a backup.
|
||||
|
||||
```bash
|
||||
docker run --name gitlab -it --rm [OPTIONS] \
|
||||
sameersbn/gitlab:8.5.7 app:rake gitlab:backup:create
|
||||
sameersbn/gitlab:8.5.8 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.
|
||||
@ -965,7 +965,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:8.5.7 app:rake gitlab:backup:restore
|
||||
sameersbn/gitlab:8.5.8 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.
|
||||
@ -974,7 +974,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the
|
||||
|
||||
```bash
|
||||
docker run --name gitlab -it --rm [OPTIONS] \
|
||||
sameersbn/gitlab:8.5.7 app:rake gitlab:backup:restore BACKUP=1417624827
|
||||
sameersbn/gitlab:8.5.8 app:rake gitlab:backup:restore BACKUP=1417624827
|
||||
```
|
||||
|
||||
## Automated Backups
|
||||
@ -999,7 +999,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:8.5.7 app:rake gitlab:env:info
|
||||
sameersbn/gitlab:8.5.8 app:rake gitlab:env:info
|
||||
```
|
||||
|
||||
You can also use `docker exec` to run raketasks on running gitlab instance. For example,
|
||||
@ -1012,7 +1012,7 @@ Similarly, to import bare repositories into GitLab project instance
|
||||
|
||||
```bash
|
||||
docker run --name gitlab -it --rm [OPTIONS] \
|
||||
sameersbn/gitlab:8.5.7 app:rake gitlab:import:repos
|
||||
sameersbn/gitlab:8.5.8 app:rake gitlab:import:repos
|
||||
```
|
||||
|
||||
Or
|
||||
@ -1031,7 +1031,7 @@ Copy all the **bare** git repositories to the `repositories/` directory of the [
|
||||
|
||||
```bash
|
||||
docker run --name gitlab -it --rm [OPTIONS] \
|
||||
sameersbn/gitlab:8.5.7 app:rake gitlab:import:repos
|
||||
sameersbn/gitlab:8.5.8 app:rake gitlab:import:repos
|
||||
```
|
||||
|
||||
Watch the logs and your repositories should be available into your new gitlab container.
|
||||
@ -1046,12 +1046,12 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Upgrading to `sameersbn/gitlab:8.5.7` 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:8.5.8` 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:8.5.7
|
||||
docker pull sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
- **Step 2**: Stop and remove the currently running image
|
||||
@ -1075,7 +1075,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] sameersbn/gitlab:8.5.7
|
||||
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:8.5.8
|
||||
```
|
||||
|
||||
## Shell Access
|
||||
|
||||
@ -9,7 +9,7 @@ postgresql:
|
||||
- /srv/docker/gitlab/postgresql:/var/lib/postgresql
|
||||
gitlab:
|
||||
restart: always
|
||||
image: sameersbn/gitlab:8.5.7
|
||||
image: sameersbn/gitlab:8.5.8
|
||||
links:
|
||||
- redis:redisio
|
||||
- postgresql:postgresql
|
||||
|
||||
@ -7,7 +7,7 @@ metadata:
|
||||
spec:
|
||||
containers:
|
||||
- name: gitlab
|
||||
image: sameersbn/gitlab:8.5.7
|
||||
image: sameersbn/gitlab:8.5.8
|
||||
env:
|
||||
- name: TZ
|
||||
value: Asia/Kolkata
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user