How to use Docker to build a Self-Host GitLab and GitLab Runner

Search for a command to run...

No comments yet. Be the first to comment.
近期因為公司的需求打算替換 Gerrit,所以用 Docker 建立了公司內部 Host 的 GitLab 和 GitLab Runner。其中這邊要提到 GitLab Runner 是用來幫 GitLab 跑 CI 的外掛,有點像是 Jenkins 的 Slave Node,用來串接 GitLab CI。 這邊主要分成三個部分 架設 GitLab GitLab Runner 串接 Auto Backup and Restore 架設 GitLab Step 1: docker pul...
現在應該開始有很多人想要踏入軟體工程的領域,但在進入這個領域之前,覺得先了解一些名詞,可以在入門時更有方向也更知道要用什麼關鍵字去找尋有用的資訊。這篇文章就是想要幫助想要入門的人理解一些軟體工程裡的專有名詞。 作業系統 這一區塊主要解釋跟作業系統層面相關的名詞 英文中文解釋 Operation system 簡稱 OS | 作業系統 | 就是電腦的作業系統,是三大作業系統分別是:Linux、Windows、macOS | | Linux | | 自由和開放原始碼的 UNI...
現在開始因為 ChatGPT 的出現,各種 AI 助手的功能都跑出來了。想想自己用了許久的環境設定也應該要來重新審視和建立新的開發環境了,僅此紀錄我個人的環境配置步驟和設定。 環境前置步驟 還原 MacBook Pro 至全新環境 macOS(全部資料刪除) 設定好初始設定後,登入 Apple ID 進入 App Store 確定 macOS 版本和預設 APP 都更新到最新 macOS 版本 到系統設定調整所有設定至個人習慣的設定 三指拖移 觸控板手勢開啟 防火牆開啟 輸入法設定...
從 ChatGPT 問世到現在,有許許多多的文章和討論出來。先從最早的 Google 要完蛋了,到後來的工作要被取代了,工程師失業了。 我就比較沒有想要馬上出來評論一下,我喜歡讓子彈飛一會兒。跟討論一下我自己比較在意的討論點。 Google 為什麼慢了? 結論:因為他需要更小心 很多人說 Google 怎麼被微軟搶先了一步。剛開始 Bing 說要加上 AI 的時候大家都在說 Google 怎麼慢了。我就馬上跑去看 OpenAI 的網站,靠北呀啊就 Azure 贊助的。那當然在正式上線 ChatG...
囤積癖
607. Sales Person 題目敘述 SQL Schema > Create table If Not Exists SalesPerson (sales_id int, name varchar(255), salary int, commission_rate int, hire_date date) Create table If Not Exists Company (com_id int, name varchar(255), city varchar(255)...
Recently, due to the team demand to replace Gerrit, I used docker to build a self-host GitLab and GitLab Runner for the company. One of the points mentioned here is GitLab Runner is a plug-in to help GitLab run CI, a bit like Jenkins Slave Node, used to cascade GitLab CI.
This is mainly divided into three parts
Build GitLab
Build and connect GitLab Runner
Set up auto backup and restore
docker pull gitlab/gitlab-ce
Create a docker-compose.yml and replace {host_ip} to the actual IP address of the server.
version: "3.6"
services:
web:
image: 'gitlab/gitlab-ce'
container_name: 'gitlab'
restart: always
hostname: {host_ip}
environment:
GITLAB_OMNIBUS_CONFIG: |
external_url 'http://{host_ip}:9090'
gitlab_rails['gitlab_shell_ssh_port'] = 2224
networks:
- gitlab-network
ports:
- '80:80'
- '443:443'
- '9090:9090'
- '2224:22'
volumes:
- '/srv/gitlab/config:/etc/gitlab'
- '/srv/gitlab/logs:/var/log/gitlab'
- '/srv/gitlab/data:/var/opt/gitlab'
networks:
gitlab-network:
name: gitlab-network
docker-compose up --build --abort-on-container-exit
At first time to start GitLab, you need to wait 3 or 5 mins. After that, you could open browser and typing {host_ip}:9090 to connect to your GitLab to reset the password. The default username is root .
At this step, you need to prepare another server for GitLab Runner. Because when GitLab Runner clone your repo that will parse issue for localhost. I am not sure how to fix this, it may due to I used dind(docker in docker) with GitLab Runner. By the way, GitLab could connect to multiple Runner and Runners could host at same server. Just remember to name different container name and mount a different volume.
Replace {runner-name} to your container name.
docker pull gitlab/gitlab-runner
docker run -d --name {runner-name} -v /var/run/docker.sock:/var/run/docker.sock -v /srv/{runner-name}/config:/etc/gitlab-runner --rm gitlab/gitlab-runner
After step 1, you could go to GitLab website to find Runner Registration Token which locate at Admin Area > Overview > Runners .

Get the token from step2 to replace {registration-token} below and run. {gitlab-ip} replace to GitLab Server IP address. {runner-name} replace to the container name which Runner want to be connected.
docker exec -it {runner-name} gitlab-runner register -n --url http://{gitlab-ip}:9090 --registration-token {registration-token} --clone-url http://{gitlab-ip}:9090 --executor docker --docker-image "docker:latest" --docker-privileged
Edit /srv/gitlab/config/gitlab.rb and add some setting. Here is my configuration to backup to AWS S3. If you want another backup place like GCP or Local, you could refer official website.
gitlab_rails['backup_keep_time'] = 86400
gitlab_rails['backup_upload_connection'] = {
'provider' => 'AWS',
'region' => 'us-west-1',
'aws_access_key_id' => {access key id},
'aws_secret_access_key' => {secret access key}
}
gitlab_rails['backup_upload_remote_directory'] = 'gitlab'
When you finish, it needs to let GitLab reload the new configuration.
docker exec -t gitlab-master gitlab-ctl reconfigure
This command will generate backup files and upload to AWS S3.
docker exec -t gitlab-master gitlab-rake gitlab:backup:create
According to the docker-compose.yml at the first step to restart GitLab
While GitLab is ready, you could download backup files from S3 to /srv/gitlab/data/backups . aws s3 cp {s3 backup file url} {backup file name}
Finally, operate restore command.
docker exec -it gitlab-master gitlab-rake gitlab:backup:restore
If you have multiple backup files at the folder then you need to specify which backup file you want to use to restore.
docker exec -it gitlab-master gitlab-rake gitlab:backup:restore BACKUP={prefix backup file name before gitlab_backup.tar}
The last thing you need to do is create a cron job to auto backup your GitLab. I use the Linux cron to handle this. I set a job to execute backup instruction at every midnight on Friday.
$ crontab -e
0 0 * * FRI docker exec -t gitlab-master gitlab-rake gitlab:backup:create