gitlab-ce安装笔记

xunknown

已于 2023-03-05 00:00:37 修改

阅读量1.3k

点赞数 1

CC 4.0 BY-SA版权

文章标签：服务器 linux ubuntu

于 2023-03-04 23:21:03 首次发布

本文链接：https://blog.youkuaiyun.com/xunknown/article/details/129310236

安装：

quick install

curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash

执行以上命令之后，就可以用apt安装了。

sudo apt install gitlab-ce

安装之后会有提示修改external_url：

alpha@mascot:~/workspace/gitlab$ sudo apt install gitlab-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-5.4.0-104 linux-headers-5.4.0-104-generic linux-image-5.4.0-104-generic linux-modules-5.4.0-104-generic linux-modules-extra-5.4.0-104-generic
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
gitlab-ce
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,247 MB of archives.
After this operation, 3,286 MB of additional disk space will be used.
Get:1 https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu focal/main amd64 gitlab-ce amd64 15.9.2-ce.0 [1,247 MB]
Fetched 1,247 MB in 1min 37s (12.8 MB/s)
Selecting previously unselected package gitlab-ce.
(Reading database ... 159036 files and directories currently installed.)
Preparing to unpack .../gitlab-ce_15.9.2-ce.0_amd64.deb ...
Unpacking gitlab-ce (15.9.2-ce.0) ...
Setting up gitlab-ce (15.9.2-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=15-9

根据提示打开/etc/gitlab/gitlab.rb修改external_url即可：

external_url 'http://0.0.0.0:9981'

修改完成之后执行：

sudo gitlab-ctl reconfigure

这个过程配置了很多东西，花的时间有点长，成功之后会提示重置root密码（这个是GItLab系统的root用户，不是Ubuntu系统的root用户）：

......

- execute /opt/gitlab/bin/gitlab-ctl hup prometheus
[2023-03-04T22:33:43+08:00] INFO: env_dir[/opt/gitlab/etc/alertmanager/env] sending restart action to runit_service[alertmanager] (delayed)
Recipe: monitoring::alertmanager
* runit_service[alertmanager] action restart (up to date)
[2023-03-04T22:33:44+08:00] INFO: env_dir[/opt/gitlab/etc/postgres-exporter/env] sending restart action to runit_service[postgres-exporter] (delayed)
Recipe: monitoring::postgres-exporter
* runit_service[postgres-exporter] action restart (up to date)
[2023-03-04T22:33:44+08:00] INFO: Cinc Client Run complete in 193.323360192 seconds

Running handlers:
[2023-03-04T22:33:44+08:00] INFO: Running report handlers
Running handlers complete
[2023-03-04T22:33:44+08:00] INFO: Report handlers complete
Infra Phase complete, 573/1539 resources updated in 03 minutes 15 seconds

Notes:
Default admin account has been configured with following details:
Username: root
Password: You didn't opt-in to print initial root password to STDOUT.
Password stored to /etc/gitlab/initial_root_password. This file will be cleaned up in first reconfigure run after 24 hours.

NOTE: Because these credentials might be present in your log files in plain text, it is highly recommended to reset the password following https://docs.gitlab.com/ee/security/reset_user_password.html#reset-your-root-password.

gitlab Reconfigured!

按照提示重置root密码：

alpha@mascot:~/workspace/gitlab$ sudo gitlab-rake "gitlab:password:reset"
Enter username: root
Enter password:
Confirm password:
Password successfully updated for user with username root.

按照参考文章的介绍，这个时候就可以访问GitLab了。

但我的访问会502出错：

502

Whoops, GitLab is taking too much time to respond.

Try refreshing the page, or going back and attempting the action again.

Please contact your GitLab administrator if this problem persists.

网上的文章说是系统内存太小了。

用sudo gitlab-ctl status命令查看（gitlab-ctl --help可以查看更多命令）：

alpha@mascot:~/workspace/gitlab$ sudo gitlab-ctl status
run: alertmanager: (pid 42577) 2107s; run: log: (pid 39330) 3276s
run: gitaly: (pid 42588) 2106s; run: log: (pid 38653) 3395s
run: gitlab-exporter: (pid 42602) 2106s; run: log: (pid 39233) 3294s
run: gitlab-kas: (pid 42604) 2106s; run: log: (pid 38930) 3381s
run: gitlab-workhorse: (pid 42614) 2105s; run: log: (pid 39116) 3314s
run: logrotate: (pid 42623) 2105s; run: log: (pid 38587) 3405s
run: nginx: (pid 42629) 2104s; run: log: (pid 39166) 3308s
run: node-exporter: (pid 42635) 2104s; run: log: (pid 39217) 3300s
run: postgres-exporter: (pid 42641) 2103s; run: log: (pid 39360) 3272s
run: postgresql: (pid 42648) 2103s; run: log: (pid 38793) 3389s
run: prometheus: (pid 42662) 2103s; run: log: (pid 39279) 3282s
run: puma: (pid 45016) 1s; run: log: (pid 39047) 3324s
run: redis: (pid 42676) 2102s; run: log: (pid 38610) 3399s
run: redis-exporter: (pid 42682) 2101s; run: log: (pid 39248) 3290s
run: sidekiq: (pid 42764) 2101s; run: log: (pid 39075) 3320s

看起来各个模块都正常启动了。

检查gitlab：

alpha@mascot:~/workspace/gitlab$ sudo gitlab-rake gitlab:check SANITIZE=true --trace
** Invoke gitlab:check (first_time)
** Invoke gitlab_environment (first_time)
** Execute gitlab_environment
** Invoke environment (first_time)
** Execute environment
** Execute gitlab:check
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.17.0 ? ... OK (14.17.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: FAILED - Internal API unreachable
gitlab-shell self-check failed
Try fixing it:
Make sure GitLab is running;
Check the gitlab-shell configuration file:
sudo -u git -H editor /opt/gitlab/embedded/service/gitlab-shell/config.yml
Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes (cluster/worker) ... 1/1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Cable config exists? ... yes
Resque config exists? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: ...
2/1 ... yes
Redis version >= 6.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.7)
Git user has default SSH configuration? ... yes
Active users: ... 1
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished