Gitlab on Docker - 屋顶上的鱼

安装docker on ubuntu

Uninstall old versions

Older versions of Docker were called docker or docker-engine. If these are installed, uninstall them:

$ sudo apt-get remove docker docker-engine docker.io

Prepare Install

$ sudo apt-get update
$ sudo apt-get install
    apt-transport-https
    ca-certificates
    curl
    software-properties-common

Add Docker’s official GPG key:

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Verify that you now have the key with the fingerprint 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88, by searching for the last 8 characters of the fingerprint.

$ sudo apt-key fingerprint 0EBFCD88

pub   4096R/0EBFCD88 2017-02-22
      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
uid                  Docker Release (CE deb) <docker@docker.com>
sub   4096R/F273FCD8 2017-02-22

$ sudo add-apt-repository
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu
   $(lsb_release -cs)
   stable"

如果是在arm的电脑上，将上面几行改为

$ sudo add-apt-repository
   "deb [arch=armhf] https://download.docker.com/linux/ubuntu
   $(lsb_release -cs)
   stable"

Install Docker CE (Community Edition)

$ sudo apt-get update
$ sudo apt-get install docker-ce

Verify Docker CE is installed correctly

$ sudo docker run hello-world

Add user to docker?

In case Docker complains about not being able to connect to the Docker daemon make sure you are in the docker group. Then you do not need to use sudo, everytime you run docker image.

sudo usermod -aG docker $USER
# *gpasswd --add $USER group-name* is same with above
# group needs to be created before with *groupadd group*
sudo service docker restart # ubuntu14.04
newgrp docker # tune current user to new group
docker ps # make sure no sudo

镜像加速

对于使用upstart的系统 (ubuntu 14.04) 而言,编辑/etc/default/docker文件,在其中的DOCKER_OPTS中添加获得的加速器配置**–registry-mirror=<加速器地址>**, e.g. how to access system-assigned url, please login to the [link](https://cr.console.aliyun.com/?spm=a2c63.p38356.879954.5.1b987c8f9giMyU): 重新启动服务。加速器地址>
```
$ sudo service docker restart
```
对于使用systemd的系统 (ubuntu 16.04),用
```
systemctl enable docker
```
启用服务后
- Old way: 编辑/etc/systemd/system/multi-user.target.wants/docker.service文件,找到ExecStart=这一行,在这行最后添加加速器地址registry-mirror=加速器地址, 如: ExecStart=/usr/bin/dockerd --registry-mirror=https://jxus37ad.mirror.aliyuncs.com.
- New way: renew or edit /etc/docker/daemon.json, and add the following content to it:
```
{
"registry-mirrors": [
 "https://hub-mirror.c.163.com",
 "https://mirror.baidubce.com"
]
}
```
  重新加载配置并且重新启动。
```
sudo systemctl daemon-reload
sudo systemctl restart docker (take a long time)
```
  For the new way, you should make sure registry-mirror is not set:
```
systemctl cat docker | grep '\-\-registry\-mirror'
```
  如果该命令有输出，那么请执行systemctl cat docker 查看 ExecStart=出现的位置，修改对应的文件内容去掉 –registry-mirror 参数及其值，并按接下来的步骤进行配置.
  
  Deploy gitlab on docker

参考gitlab官方网站关于docker的文档

pull镜像

$ sudo docker pull gitlab/gitlab-ce:latest

启动Gitlab

用下面的命令启动一个默认配置的Gitlab。如果我们只在本机测试使用的话，将hostname替换为localhost。如果需要让外部系统也能访问的话使用外网IP地址。

$ sudo docker run --detach \
    --hostname 127.0.0.1 \
    --publish 443:443 --publish 80:80 --publish 22:22 \
    --name gitlab \
    --restart always \
    --volume /srv/gitlab/config:/etc/gitlab \
    --volume /srv/gitlab/logs:/var/log/gitlab \
    --volume /srv/gitlab/data:/var/opt/gitlab \
    gitlab/gitlab-ce:latest

docker端口映射

ip:hostport:containerport   #指定ip、指定主机port、指定容器port
ip::containerport           #指定ip、未指定主机port、指定容器port
hostport:container          #未指定ip port、指定主机port、指定容器port

可以采用以下的端口映射：

$ sudo docker run --detach \
    --hostname 127.0.0.1 \
    --publish 4430:443 --publish 8000:80 --publish 2200:22 \
    --name gitlab \
    --restart always \
    --volume /srv/gitlab/config:/etc/gitlab \
    --volume /srv/gitlab/logs:/var/log/gitlab \
    --volume /srv/gitlab/data:/var/opt/gitlab \
    gitlab/gitlab-ce:latest

进人运行的容器（docker exec -it gitlab /bin/bash）

Set external_url :

For HTTP external_url “http://gitlab.example.com:8000”
For HTTPS (notice the https) external_url “https://gitlab.example.com:8000”

Set gitlab_shell_ssh_port :

gitlab_rails[‘gitlab_shell_ssh_port’] = 2200

Following the above example you will be able to reach GitLab from your web browser under hostIP:8000 and push using SSH under the port 2200.

使用sudo gitlab-ctl reconfigure更新docker配置。

不知道有没有必要：Just allow git to login by ssh. Edit /etc/ssh/sshd_config, and add this content: AllowUsers git. 可以使用以下方法验证git服务器的ssh功能

增加内容：git服务器ssh验证

ssh -p <port_num> git@192.168.1.254

如果以上的结果显示

Welcome to GitLab, <UserName>!
Connection to 192.168.1.254 closed.

一直出现restarting

使用sudo docker logs <container_name>查看容器状态
如果出现

exec user process caused "exec format error"

说明下载的镜像不正确，不是适合x86或者arm的

gitlab迁移到another PC

在原来PC上使用一下命令，并copy到新PC上

docker export -o gitlab.docker

在新PC上使用

docker import gitlab.docker gitlab:cpone

此时完成image拷贝到新电脑的过程，然后按照启动Gitlab中的步骤，启动container for gitlab.
最后一步就是复制数据到新电脑上
将gitlab整个文件夹打包/压缩后复制到新PC。 Here, I wanna add something involving the difference between save and export:

save command will fetch an image as opposite to load. such as docker save -o <user-defined-name> <image-id-name>.
export command will fetch the whole container including filesystem as opposite to import. such as docker export -o <user-defined-name> <container-id-name>.
run command will spin up a new container for you to use.
exec command will allow you to use a container that is already running.

Remove and Restore for DOCKER Gitlab installations

在原来电脑上需要完成的工作：

You have run sudo gitlab-ctl reconfigure at least once. 保证配置文件生效，所有配置文件和gitlab配置相同，可以不使用。

docker exec -t <container name> gitlab-rake gitlab:backup:create //backup gitlab
cp /etc/gitlab/gitlab-secrets.json ~/   //This file contains the database encryption key, CI/CD variables, and variables used for two-factor authentication.
cp /etc/gitlab/gitlab.rb ~/
cp -r /etc/ssh ~/    # backup ssh key

上面的gitlab-secrets.json需要单独备份到本地，如果丢失可能导致：GitLab Runners will lose access to your GitLab server. 代替地，可以选择将整个/etc/gitlab和/etc/ssh文件夹备份。

在新迁移的电脑上需要完成的工作：

You have installed the exact same version and type (CE/EE) of GitLab Omnibus with which the backup was created. 在dockerImage上查找一定版本tag，即gitlab/gitlab-ce:{tag_name}。
GitLab is running. If not, start it using sudo gitlab-ctl start.

#stop the processes that are connected to the database, leave the rest of GitLab running
sudo gitlab-ctl stop unicorn

sudo gitlab-ctl stop sidekiq

#verify the two processes are down
sudo gitlab-ctl status

#overwrite the contents of your GitLab database!
sudo gitlab-rake gitlab:backup:restore BACKUP=1493107454_2018_04_25_10.6.4-ce

Make sure your backup tarball (1493107454_2018_04_25_10.6.4-ce_gitlab_backup.tar) is in the backup directory described in the gitlab.rb configuration gitlab_rails[‘backup_path’]. The default is /var/opt/gitlab/backups.

Restore /etc/gitlab/gitlab-secrets.json and /etc/ssh if necessary as mentioned above.

#Restart and check GitLab
sudo gitlab-ctl restart

sudo gitlab-rake gitlab:check SANITIZE=true

Make sure the server is OK in chrome with username and passward.

Issues on Gitlab install

docker logs -f gitlab shows ERROR: relation “plans” does not exist at character 183.

Use docker exec -it gitlab gitlab-ctl restart gitlab-monitor to restart gitlab-monitor for shutting down gitlab-monitor to quiet the warning noise. The following command returns ok: run: gitlab-monitor: (pid 1942) 1s, no need to reboot and your gitlab server should be OK!

Disable docker autostart container

docker inspect {my-container} //Look for RestartPolicy in the output
docker update --restart=no {my-container}

docker basic operations

remove all container whether it is running or not

docker container stop $(docker container ls -aq)
docker container prune

Running GUI inside Docker Container

There can be two types of applications that you can containerise:

Application that run as a background service(like a Database, WebServer, etc)
GUI Applications that run in the foreground.

For the second one(GUI Application), we need to have a XServer which is available as part of every Linux Desktop Environment. But within a Container we don’t have any XServer – so we will

share the Host’s XServer with the container by creating a volume via --volume="$HOME/.Xauthority:/root/.Xauthority:rw".
share the Host’s DISPLAY environment variable to the container via --env="DISPLAY".
run container with host network dirver with --net=host.

Let’s take an example. Use the Dockerfile to build an image via docker build -t gui-test:latest ..

# Dockerfile
FROM ubuntu:16.04
RUN apt-get update && apt-get install xlogo
CMD ["/usr/bin/xlogo"]

Let’s run the image via docker run --net=host --env="DISPLAY" --volume="$HOME/.Xauthority:/root/.Xauthority:rw" gui-test:latest.

Donation

If you think this useful for you, you can donate for me. Thank you for your support!

weixin zhifubao