2.gitlab-ce
0.注意事项
注意：gitlab-ce 镜像仅支持 x86-64 架构
Debian/Ubuntu 用户
1.首先信任 GitLab 的 GPG 公钥
curl -fsSL https://packages.gitlab.com/gpg.key | sudo gpg --dearmor > /usr/share/keyrings/gitlab_gitlab-ce-archive-keyring.gpg
root@json:~# curl -fsSL https://packages.gitlab.com/gpg.key | sudo gpg --dearmor > /usr/share/keyrings/gitlab_gitlab-ce-archive-keyring.gpg
root@json:~#
2.快速配置镜像源(参考)
cat <<'EOF' > /etc/apt/sources.list.d/gitlab-ce.list
deb [signed-by=/usr/share/keyrings/gitlab_gitlab-ce-archive-keyring.gpg] https://mirror.nju.edu.cn/gitlab-ce/debian bookworm main
EOF
3.安装 gitlab-ce
root@json:~# sudo apt-get update
Get:1 https://mirror.nju.edu.cn/gitlab-ce/ubuntu jammy InRelease [23.3 kB]
Hit:2 https://mirrors.ustc.edu.cn/ubuntu oracular InRelease
Hit:3 https://mirrors.ustc.edu.cn/ubuntu oracular-updates InRelease
Hit:4 https://mirrors.ustc.edu.cn/ubuntu oracular-backports InRelease
Ign:5 https://mirror.nju.edu.cn/gitlab-ce/ubuntu jammy/main amd64 Packages
Hit:6 http://security.ubuntu.com/ubuntu oracular-security InRelease
Get:5 https://mirror.nju.edu.cn/gitlab-ce/ubuntu jammy/main amd64 Packages [39.7 kB]
Hit:7 https://download.docker.com/linux/ubuntu oracular InRelease
Fetched 39.7 kB in 1s (41.6 kB/s)
Reading package lists... Done
root@json:~#
root@json:~#
root@json:~# sudo apt-get install gitlab-ce
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libevent-2.1-7t64
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
gitlab-ce
0 upgraded, 1 newly installed, 0 to remove and 85 not upgraded.
Need to get 1379 MB of archives.
After this operation, 3742 MB of additional disk space will be used.
Get:1 https://mirror.nju.edu.cn/gitlab-ce/ubuntu jammy/main amd64 gitlab-ce amd64 17.9.0-ce.0 [1379 MB]
Fetched 1379 MB in 50s (27.7 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package gitlab-ce.
(Reading database ... 162781 files and directories currently installed.)
Preparing to unpack .../gitlab-ce_17.9.0-ce.0_amd64.deb ...
Unpacking gitlab-ce (17.9.0-ce.0) ...
Setting up gitlab-ce (17.9.0-ce.0) ...
It looks like GitLab has not been configured yet; skipping the upgrade script.
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,,*****,,,,,,,,,.
,,,,,,,****,,,,,,
.,,,***,,,,
,*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Thank you for installing GitLab!
GitLab was unable to detect a valid hostname for your instance.
Please configure a URL for your GitLab instance by setting `external_url`
configuration in /etc/gitlab/gitlab.rb file.
Then, you can start your GitLab instance by running the following command:
sudo gitlab-ctl reconfigure
For a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
Help us improve the installation experience, let us know how we did with a 1 minute survey:
https://gitlab.fra1.qualtrics.com/jfe/form/SV_6kVqZANThUQ1bZb?installation=omnibus&release=17-9
Scanning processes...
Scanning linux images...
Running kernel seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
4.配置gitlab-ce
5.查看状态
root@json:~# gitlab-ctl status
run: alertmanager: (pid 17150) 1287s; run: log: (pid 16685) 1338s
run: gitaly: (pid 17130) 1289s; run: log: (pid 15487) 1484s
run: gitlab-exporter: (pid 17069) 1290s; run: log: (pid 16515) 1356s
run: gitlab-kas: (pid 24670) 0s; run: log: (pid 15721) 1467s
run: gitlab-workhorse: (pid 17034) 1292s; run: log: (pid 16340) 1374s
run: logrotate: (pid 15407) 1499s; run: log: (pid 15416) 1497s
run: nginx: (pid 17051) 1291s; run: log: (pid 16416) 1367s
run: node-exporter: (pid 17059) 1291s; run: log: (pid 16475) 1362s
run: postgres-exporter: (pid 17167) 1287s; run: log: (pid 16752) 1331s
run: postgresql: (pid 15527) 1476s; run: log: (pid 15556) 1473s
run: prometheus: (pid 17105) 1289s; run: log: (pid 16630) 1344s
run: puma: (pid 16213) 1388s; run: log: (pid 16239) 1385s
run: redis: (pid 15437) 1493s; run: log: (pid 15446) 1492s
run: redis-exporter: (pid 17078) 1290s; run: log: (pid 16586) 1348s
run: sidekiq: (pid 16268) 1381s; run: log: (pid 16290) 1379s
root@json:~#
6.查看登入root密码
root@json:~# cat /etc/gitlab/initial_root_password
# WARNING: This value is valid only in the following conditions
# 1. If provided manually (either via `GITLAB_ROOT_PASSWORD` environment variable or via `gitlab_rails['initial_root_password']` setting in `gitlab.rb`, it was provided before database was seeded for the first time (usually, the first reconfigure run).
# 2. Password hasn't been changed manually, either via UI or via command line.
#
# If the password shown here doesn't work, you must reset the admin password following https://docs.gitlab.com/ee/security/reset_user_password.html#reset-your-root-password.
Password: RsO+VZOi9D/dA8OmH5ZKkY6cgVzKtQcsddg/yLy+7s8=
# NOTE: This file will be automatically deleted in the first reconfigure run after 24 hours.
root@json:~#
7.web登入
8.关闭gitlab-ce开启启动
root@json:~# systemctl status gitlab-runsvdir.service
● gitlab-runsvdir.service - GitLab Runit supervision process
Loaded: loaded (/usr/lib/systemd/system/gitlab-runsvdir.service; enabled; preset: enabled)
Active: active (running) since Mon 2025-02-24 13:17:58 CST; 52min ago
Invocation: 60e6f21475aa47dd854ff99fd139efc9
Main PID: 15381 (runsvdir)
Tasks: 31 (limit: 4915)
Memory: 260.4M (peak: 3.9G)
CPU: 26min 16.495s
CGroup: /system.slice/gitlab-runsvdir.service
├─15381 runsvdir -P /opt/gitlab/service "log: ................................................................................................................................................>
├─15405 runsv logrotate
├─15416 svlogd -tt /var/log/gitlab/logrotate
├─15435 runsv redis
├─15446 svlogd -tt /var/log/gitlab/redis
├─15456 runsv gitaly
├─15487 svlogd /var/log/gitlab/gitaly
├─15525 runsv postgresql
├─15556 svlogd -tt /var/log/gitlab/postgresql
├─15694 runsv gitlab-kas
├─15721 svlogd -tt /var/log/gitlab/gitlab-kas
├─16210 runsv puma
├─16239 svlogd -tt /var/log/gitlab/puma
├─16266 runsv sidekiq
├─16290 svlogd /var/log/gitlab/sidekiq
├─16320 runsv gitlab-workhorse
├─16340 svlogd /var/log/gitlab/gitlab-workhorse
├─16384 runsv nginx
├─16416 svlogd -tt /var/log/gitlab/nginx
├─16457 runsv node-exporter
├─16475 svlogd -tt /var/log/gitlab/node-exporter
├─16509 runsv gitlab-exporter
├─16515 svlogd -tt /var/log/gitlab/gitlab-exporter
├─16553 runsv redis-exporter
├─16586 svlogd -tt /var/log/gitlab/redis-exporter
├─16610 runsv prometheus
├─16630 svlogd -tt /var/log/gitlab/prometheus
├─16661 runsv alertmanager
├─16685 svlogd -tt /var/log/gitlab/alertmanager
├─16721 runsv postgres-exporter
└─16752 svlogd -tt /var/log/gitlab/postgres-exporter
Feb 24 13:17:58 json systemd[1]: Started gitlab-runsvdir.service - GitLab Runit supervision process.
9.手工启动gitlab-ce
#如果runsv没有启动，就无法使用gitlab-ctl start启动gitlab
sudo gitlab-ctl start
sudo systemctl start gitlab-runsvdir.service
sudo gitlab-ctl start
sudo gitlab-ctl status
json@json:~$ sudo gitlab-ctl start
[sudo] password for json:
fail: alertmanager: runsv not running
fail: gitaly: runsv not running
fail: gitlab-exporter: runsv not running
fail: gitlab-kas: runsv not running
fail: gitlab-workhorse: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: node-exporter: runsv not running
fail: postgres-exporter: runsv not running
fail: postgresql: runsv not running
fail: prometheus: runsv not running
fail: puma: runsv not running
fail: redis: runsv not running
fail: redis-exporter: runsv not running
fail: sidekiq: runsv not running
json@json:~$
json@json:~$
json@json:~$ sudo systemctl start gitlab-runsvdir.service
json@json:~$
json@json:~$ sudo gitlab-ctl start
ok: run: alertmanager: (pid 34727) 3s
ok: run: gitaly: (pid 34723) 3s
ok: run: gitlab-exporter: (pid 34702) 3s
ok: run: gitlab-kas: (pid 34810) 1s
ok: run: gitlab-workhorse: (pid 34724) 3s
ok: run: logrotate: (pid 34722) 3s
ok: run: nginx: (pid 34714) 3s
ok: run: node-exporter: (pid 34720) 3s
ok: run: postgres-exporter: (pid 34703) 3s
ok: run: postgresql: (pid 34717) 3s
ok: run: prometheus: (pid 34721) 3s
ok: run: puma: (pid 34704) 3s
ok: run: redis: (pid 34718) 3s
ok: run: redis-exporter: (pid 34728) 3s
ok: run: sidekiq: (pid 34719) 3s
json@json:~$
json@json:~$ sudo gitlab-ctl status
run: alertmanager: (pid 34727) 11s; run: log: (pid 34715) 11s
run: gitaly: (pid 34723) 11s; run: log: (pid 34708) 11s
run: gitlab-exporter: (pid 34702) 11s; run: log: (pid 34697) 11s
run: gitlab-kas: (pid 34873) 2s; run: log: (pid 34698) 11s
run: gitlab-workhorse: (pid 34724) 11s; run: log: (pid 34716) 11s
run: logrotate: (pid 34722) 11s; run: log: (pid 34707) 11s
run: nginx: (pid 34714) 11s; run: log: (pid 34710) 11s
run: node-exporter: (pid 34720) 11s; run: log: (pid 34712) 11s
run: postgres-exporter: (pid 34703) 11s; run: log: (pid 34699) 11s
run: postgresql: (pid 34717) 11s; run: log: (pid 34709) 11s
run: prometheus: (pid 34721) 11s; run: log: (pid 34705) 11s
run: puma: (pid 34704) 11s; run: log: (pid 34700) 11s
run: redis: (pid 34718) 11s; run: log: (pid 34711) 11s
run: redis-exporter: (pid 34728) 11s; run: log: (pid 34713) 11s
run: sidekiq: (pid 34719) 11s; run: log: (pid 34706) 11s