# 使用docker安装gitlab
# 1、安装gitlab
# 1.1 创建gitlab数据目录
首先,需要为gitlab的数据创建一个目录,用来存储gitlab在运行过程中产生的数据。
sudo mkdir -p /data/gitlab #/data/gitlab可以修改成合适的目录
1
# 1.2 搜索gitlab
docker search gitlab
1
# 1.3 拉取gitlab
# amd
docker pull gitlab/gitlab-ce
# arm
docker pull yrzr/gitlab-ce-arm64v8:16.0.4-ce.0
1
2
3
4
2
3
4
# 1.4 启动gitlab
# 最新版
docker run -d -p 8099:80 -p 222:22 --name gitlabs --restart always -v /data/gitlab/etc:/etc/gitlab -v /data/gitlab/log:/var/log/gitlab -v /data/gitlab/data:/var/opt/gitlab gitlab/gitlab-ce
# 指定版本
sudo docker run -d -p 8099:80 -p 222:22 --name gitlab --restart always -v /data/gitlab/etc:/etc/gitlab -v /data/gitlab/log:/var/log/gitlab -v /data/gitlab/data:/var/opt/gitlab yrzr/gitlab-ce-arm64v8:16.3.3-ce.0
1
2
3
4
5
2
3
4
5
参数说明:
-i 以交互模式运行容器,通常与 -t 同时使用命令解释:
-d 后台运行容器,并返回容器ID
-p 8099:80 将容器内80端口映射至宿主机9980端口,这是访问gitlab的端口
-p 222:22 将容器内22端口映射至宿主机222端口,这是访问ssh的端口
-v ./gitlab/etc:/etc/gitlab 将容器/etc/gitlab目录挂载到宿主机./gitlab/etc目录下,若宿主机内此目录不存在将会自动创建,其他两个挂载同这个一样
--restart always 容器自启动
--privileged=true 让容器获取宿主机root权限
--name gitlab-test 设置容器名称为gitlab
gitlab/gitlab-ce 镜像的名称,这里也可以写镜像ID
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
# 2、配置gitlab
# 2.1 修改配置文件
vim /data/gitlab/etc/gitlab.rb
1
或者进入容器再修改:
sudo docker exec -it gitlabs /bin/bash
vim /etc/gitlab/gitlab.rb
1
2
2
external_url 'http://服务器ip:端口/'
gitlab_rails['gitlab_ssh_host'] = '服务器ip'
gitlab_rails['gitlab_shell_ssh_port'] = 222
1
2
3
2
3
若不配置则默认 80 端口 和 22 端口(ssh),本人使用了端口映射所以默认不配置,只需要服务器开放8099和222端口。
改完配置后需要重载配置
# 2.2 修改密码
查看初始密码:
vim /data/gitlab/etc/initial_root_password
1
或者进入容器查看:
sudo docker exec -it gitlabs /bin/bash
vim /etc/gitlab/initial_root_password
1
2
2
进入gitlab网站,使用 root 账号和初始密码登录,然后再修改密码
第二种办法:
(本人使用该方法未通过,在执行 gitlab-rails console -e production
或者 gitlab-rails console
都直接卡死在页面上)
# 进入容器内部
docker exec -it gitlab /bin/bash
# 进入控制台
gitlab-rails console -e production
# 查询id为1的用户,id为1的用户是超级管理员
user = User.where(id:1).first
# 修改密码为root1AQ@
user.password='root1AQ@'
# 保存
user.save!
# 退出
exit
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2
3
4
5
6
7
8
9
10
11
12
13
14
# 3、设置邮箱
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "smtp.qq.com"
gitlab_rails['smtp_port'] = 465
gitlab_rails['smtp_user_name'] = "xxx@qq.com"
gitlab_rails['smtp_password'] = "hlldwcjoqsc******"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['smtp_tls'] = true
gitlab_rails['gitlab_email_from'] = 'xxx@qq.com'
gitlab_rails['smtp_domain'] = "qq.com"
1
2
3
4
5
6
7
8
9
10
2
3
4
5
6
7
8
9
10
# 4、轻量化运行
# 关闭容器仓库功能
gitlab_rails['gitlab_default_projects_features_container_registry'] = false
gitlab_rails['registry_enabled'] = false
registry['enable'] = false
registry_nginx['enable'] = false
# 包仓库、依赖管理
gitlab_rails['packages_enabled'] = false
gitlab_rails['dependency_proxy_enabled'] = false
# GitLab Pages
gitlab_pages['enable'] = false
pages_nginx['enable'] = false
# 关闭监控和性能基准相关功能
prometheus_monitoring['enable'] = false
alertmanager['enable'] = false
node_exporter['enable'] = false
redis_exporter['enable'] = false
postgres_exporter['enable'] = false
pgbouncer_exporter['enable'] = false
gitlab_exporter['enable'] = false
grafana['enable'] = false
sidekiq['metrics_enabled'] = false
# 针对应用的性能分析和上报
gitlab_rails['usage_ping_enabled'] = false
gitlab_rails['sentry_enabled'] = false
grafana['reporting_enabled'] = false
# GitLab KAS
gitlab_kas['enable'] = false
gitlab_rails['gitlab_kas_enabled'] = false
# Terraform
gitlab_rails['terraform_state_enabled'] = false
# Kerberos 文档说EE only,但是默认值为 true
gitlab_rails['kerberos_enabled'] = false
# Sentinel
sentinel['enable'] = false
# Mattermost
mattermost['enable'] = false
mattermost_nginx['enable'] = false
# 禁用 PUMA 集群模式
puma['worker_processes'] = 0
puma['min_threads'] = 1
puma['max_threads'] = 2
# 降低后台守护进程并发数
sidekiq['max_concurrency'] = 5
# 关闭电子邮件相关功能
gitlab_rails['smtp_enable'] = false
gitlab_rails['gitlab_email_enabled'] = false
gitlab_rails['incoming_email_enabled'] = false
# 关闭ci
gitlab_ci['gitlab_ci_all_broken_builds'] = false
gitlab_ci['gitlab_ci_add_pusher'] = false
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
# 5、容器命令
sudo docker restart gitlab # 重启容器
docker rm -f gitlab # 删除容器
exit # 退出容器
gitlab-ctl start # 启动全部服务
gitlab-ctl restart # 重启全部服务
gitlab-ctl stop #停止全部服务
gitlab-ctl restart nginx #重启单个服务,如重启nginx
gitlab-ctl status # 查看服务状态
gitlab-ctl reconfigure #使配置文件生效
gitlab-ctl show-config #验证配置文件
gitlab-ctl uninstall #删除gitlab(保留数据)
gitlab-ctl cleanse #删除所有数据,从新开始
gitlab-ctl tail <service name>查看服务的日志
gitlab-ctl tail nginx #如查看gitlab下nginx日志
gitlab-rails console #进入控制台
# gitlab 数据目录
/var/opt/gitlab
# 命令目录
/opt/gitlab/bin
gitlab-backup gitlab-healthcheck gitlab-rails gitlab-redis-cli
gitlab-ctl gitlab-psql gitlab-rake gitlab-ruby
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# 6、参考
https://zhuanlan.zhihu.com/p/413217715
# 7、常见错误及操作
# 7.1 postgresql 数据库启动失败引起的 502 页面异常
(1)查看服务状态
进入容器 sudo docker exec -it gitlabs /bin/bash
后查看服务状态 gitlab-ctl status
run: gitaly: (pid 278) 90s; run: log: (pid 276) 90s
run: gitlab-workhorse: (pid 338) 88s; run: log: (pid 336) 88s
run: logrotate: (pid 277) 90s; run: log: (pid 275) 90s
run: nginx: (pid 339) 88s; run: log: (pid 337) 88s
down: postgresql: 1s, normally up, want up; run: log: (pid 334) 88s
run: puma: (pid 551) 13s; run: log: (pid 331) 88s
run: redis: (pid 280) 90s; run: log: (pid 279) 90s
run: sidekiq: (pid 560) 10s; run: log: (pid 330) 88s
run: sshd: (pid 38) 101s; run: log: (pid 33) 101s
1
2
3
4
5
6
7
8
9
2
3
4
5
6
7
8
9
可以看到 postgresql
服务是 down
的状态
(2)查看服务日志
输入命令 gitlab-ctl tail postgresql
,提示:
database system is shut down
2023-10-25_10:22:35.73532 LOG: starting PostgreSQL 13.11 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, 64-bit
2023-10-25_10:22:35.73535 FATAL: lock file "/var/opt/gitlab/postgresql/.s.PGSQL.5432.lock" is empty
2023-10-25_10:22:35.73535 HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
1
2
3
4
2
3
4
(3)删除遗留的 lock 和 pid 文件
进入容器找到 /var/opt/gitlab/postgresql/.s.PGSQL.5432.lock
文件并删除
重启服务,然后出现提示:
lock file "postmaster.pid" is empty
2023-10-25_09:17:25.83247 HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
1
2
2
在 /var/opt/gitlab/postgresql/data
目录下找到 postmaster.pid
文件并删除
重启服务,然后出现提示:
database system was shut down at 2023-09-27 14:22:07 GMT
2023-10-25_10:31:52.16432 LOG: invalid record length at 0/6B355F0: wanted 24, got 0
2023-10-25_10:31:52.16440 LOG: invalid primary checkpoint record
2023-10-25_10:31:52.16447 PANIC: could not locate a valid checkpoint record
2023-10-25_10:31:52.49977 LOG: startup process (PID 394) was terminated by signal 6: Aborted
2023-10-25_10:31:52.49979 LOG: aborting startup due to startup process failure
2023-10-25_10:31:52.49980 LOG: database system is shut down
2023-10-25_10:31:53.63088 LOG: starting PostgreSQL 13.11 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, 64-bit
1
2
3
4
5
6
7
8
2
3
4
5
6
7
8
使用命令修复:
# Postgres >= 10
pg_resetwal /var/opt/gitlab/postgresql/data
# Postgres < 10
pg_resetxlog /var/opt/gitlab/postgresql/data
# 可能会提示需要使用 Postgres 超级管理员的权限来使用该命令,进入 Postgres 超级管理员用户权限
su - gitlab-psql # 用户名可以通过进入 /var/opt/gitlab/postgresql/data 目录,使用 ll 命令查看
# 然后输入命令
pg_resetwal /var/opt/gitlab/postgresql/data
# 强制更新
pg_resetwal -f /var/opt/gitlab/postgresql/data
1
2
3
4
5
6
7
8
9
10
11
12
13
2
3
4
5
6
7
8
9
10
11
12
13
# 7.2 使用命令行修改普通用户为管理员
cat /var/opt/gitlab/gitlab-rails/etc/database.yml
su - gitlab-psql
psql -h /var/opt/gitlab/postgresql -d gitlabhq_production
$ select id,username,email,admin from users;
$ select id,username,email,admin from users where username='sanyer';
$ update users set admin='t' where username='sanyer';
# 出现 UPDATE 1 则修改成功
1
2
3
4
5
6
7
8
2
3
4
5
6
7
8
# 8、备份
# 进入容器内部
sudo docker exec -it gitlab /bin/bash
# 开始备份
gitlab-backup create
# 查看备份文件
cd /data/gitlab/data/backups
1712848104_2024_04_11_16.3.3_gitlab_backup.tar
# 本机还原
gitlab-backup restore
1
2
3
4
5
6
7
8
9
10
11
12
2
3
4
5
6
7
8
9
10
11
12
# 9、迁移新服务器
# 9.1 先决条件
- 目标 GitLab 实例必须已在工作
- 目标 GitLab 实例必须具有完全相同的版本,备份还原到与创建备份时完全相同的 GitLab 版本和类型(CE 或 EE)。例如,CE 16.3.3
- 必须还原 GitLab 秘钥,即
/data/gitlab/etc
配置中的文件 - 清空挂载点目录
/data/gitlab/data
和/data/gitlab/log
# 9.2 开始还原
sudo docker run -d -p 8099:80 -p 222:22 --name gitlab --restart always -v /data/gitlab/etc:/etc/gitlab -v /data/gitlab/log:/var/log/gitlab -v /data/gitlab/data:/var/opt/gitlab yrzr/gitlab-ce-arm64v8:16.3.3-ce.0
# 容器创建成功后,复制备份文件到 /data/gitlab/data/backups 目录
sudo cp 1712848104_2024_04_11_16.3.3_gitlab_backup.tar /data/gitlab/data/backups
# 进入容器内部
sudo docker exec -it gitlab /bin/bash
# 设置备份文件权限
chown git:git /var/opt/gitlab/backups/1712848104_2024_04_11_16.3.3_gitlab_backup.tar
# 停止连接到数据库的进程
gitlab-ctl stop puma
gitlab-ctl stop sidekiq
# 指定要备份的 ID 恢复
gitlab-backup restore BACKUP=1712848104_2024_04_11_16.3.3
# 中间会弹出几次确认事件,输入 yes 即可
# 重启后,页面502,需等待系统重启5分钟左右
gitlab-ctl restart
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
参考:https://docs.gitlab.com/ee/administration/backup_restore/restore_gitlab.html