Build GitLab / Mattermost with DockerForWindows

Introduction

I wanted to try various things using the Mattermost API, and when I tried to build a GitLab environment quickly, I was addicted to it unexpectedly, so I will leave what I did. What I want to do is build a GitLab environment using DockerForWindows.

Things that move

I put it on GitHub. (https://github.com/shimi58/CentOS8_GitLab) However, the Mattermost setting changes each time you build it, so the procedure described below is required.

Operation check environment	version
Windows10 Home Edition	Version 2004
Docker for Windows	2.4.0.0

GitLab's Docker is not officially supported by Docker For Windows. .. Port forwarding doesn't work (80 → 80 works, but 8080 → 80 doesn't connect), so I wonder if that's the case.

Environment

Build CentOS 8 on Docker

I will describe it in the Dockerfile. The result is as follows.

FROM centos:8

#Localizing into Japanese
RUN rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial && \
    dnf -y upgrade && \
    dnf -y install glibc-locale-source && \
    dnf clean all && \
    localedef -f UTF-8 -i ja_JP ja_JP.UTF-8 && \
    ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime

#C LANG for Gitlab installation.UTF-Change to 8
ENV LANG="C.UTF-8" \
    LANGUAGE="ja_JP:ja" \
    LC_ALL="ja_JP.UTF-8"

#root password setting
RUN echo "root:root" | chpasswd

# =====
# BASE packages
# =====
RUN dnf install -y  openssl openssl-devel openssh openssh-server wget sudo unzip  which tree git firewalld

# =====
#Install GitLab CE
# =====
RUN curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash

RUN dnf install -y gitlab-ce

`docker-compose.yml`


version: '3'
services:
  centos8:
    container_name: "centos8"
    build: ./
    tty: true
    privileged: true
    command: /sbin/init   
    ports:
      - "2222:22"
      - "9080:9080" #For GitLab
      - "9081:9081" #For GitLab Mattermost
      - '10443:443'
    volumes:
      #Persistence according to the formula
      - './srv/gitlab/config:/etc/gitlab'   #Place GitLab definition file
      - './srv/gitlab/logs:/var/log/gitlab' #GItLab log file output
      - './srv/gitlab/data:/var/opt/gitlab' #GItLab data storage

Supplement

--Japanese environment settings

```
#Localizing into Japanese
RUN rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial && \
    dnf -y upgrade && \
    dnf -y install glibc-locale-source && \
    dnf clean all && \
    localedef -f UTF-8 -i ja_JP ja_JP.UTF-8 && \
    ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime

#C LANG for Gitlab installation.UTF-Change to 8
ENV LANG="C.UTF-8" \
    LANGUAGE="ja_JP:ja" \
    LC_ALL="ja_JP.UTF-8"
```

I referred to this (https://qiita.com/polarbear08/items/e5c00869c7566db5f7b8). If you do not set LANG to C.UTF-8, it will stop around DB migration of "gitlab-ctl reconfigure", so be careful.

--Install GitLab CE

```cmd
RUN curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash

RUN dnf install -y gitlab-ce
```

This is the official procedure. (Note that the official sample is gitlab-ee)

--Data persistence

```docker-compose.yml
    volumes:
      #Persistence according to the formula
      - './srv/gitlab/config:/etc/gitlab'   #Place GitLab definition file
      - './srv/gitlab/logs:/var/log/gitlab' #GItLab log file output
      - './srv/gitlab/data:/var/opt/gitlab' #GItLab data storage
```

If this is set, the data will be retained even if the container is dropped.

Construction procedure

Place the above Dockerfile and docker-compose.yml in any directory.
Move to the placed directory and start the container
```
docker-compose up -d
```

Place gitlab.rb in the specified folder

srv
└─gitlab
    ├─config
    │      gitlab.rb
    │
    ├─data
    └─logs

This file can be found here (https://github.com/shimi58/CentOS8_GitLab).

At first, it may be better to comment out the Mattermost setting described later. (It may not appear in Applications or you may not be able to follow the procedure)

Set the port of GitLab
```
external_url 'http://localhost:9080'
```

Enable GitLab Mattermost

mattermost_external_url 'http://localhost:9081'
mattermost['enable'] = true

If you log in from the CLI of Docker For Windows, the LANG settings will not be reflected, so you are logged in from powershell.
LANG setting is as expected

Reflect GitLab settings

sudo /opt/gitlab/embedded/bin/runsvdir-start &
gitlab-ctl reconfigure

If "gitlab-ctl reconfigure" is used alone, it will stop in the middle, so refer to here (https://teratail.com/questions/229107) and run runsvdir-start in the background before reconfigure. The first time it takes less than 5 minutes.

After the reflection, access GitLab
```
http://localhost:9080
```

Confirm that you can log in

--Mattermost can also be displayed at this timing

    ```url
    http://localhost:9081
    ```

Supplement

――After that, it will be the procedure of Mattermost SSO cooperation

After completing the initial password settings, log in

Initial ID is "root"

Check the Mattermost settings --Move to "Admin Area"-> "Applications" --If there is already a definition for Mattermost, use it, if not, create a new one (* It will not be displayed if the mattermost setting in gitlab.rb is enabled)

I referred to this (https://qiita.com/TomoyukiSugiyama/items/0d828ee2325095a7f247).

Reflect the "Application ID" and "Secret" confirmed above in gitlab.rb At the same time, add the necessary settings

mattermost['gitlab_enable'] = true #SSO enabled
mattermost['gitlab_id'] = "5e7f43cdf588e92c8b0ca589832c64dd5094969c5848667a09e50ffe4834c065"      #Application ID
mattermost['gitlab_secret'] = "23791f7219f6782f38c9c1f462c5e715e88216ee13d3513a122dc9c302ba130b"  #secret
mattermost['gitlab_auth_endpoint'] = "http://localhost:9080/oauth/authorize" #Enter the URL of GitLab
mattermost['gitlab_token_endpoint'] = "http://localhost:9080/oauth/token"    #Enter the URL of GitLab
mattermost['gitlab_user_api_endpoint'] = "http://localhost:9080/api/v4/user" #Enter the URL of GitLab

Reflect GitLab settings
```
gitlab-ctl reconfigure
```
From Mattermost, select "Sign in with GitLab" and log in

If communication is successful, the screen will change to this screen, so select "Anthorize".

Confirm that the transition to the Mattermost screen is displayed.

finally

GitLab built this time is heavy even with CORE i7 and memory 16G.

I'm doing my best with both CPU memory. .. With that said, the foundation for the Mattermost API is finally ready, so I would like to touch the API next.

2020/10/18 postscript

After rebuilding the container, restore persistent data. Gitlab-ctl reconfigure is required to reflect.