GitLab CI转轮无法连接到kubernetes中的unix：///var/run/docker.sock

Question

GitLab在kubernetes集群中运行。运行器不能用构建工件来构建Docker镜像。我已经尝试了几种方法来解决这个问题，但没有运气。下面是一些CONFIGS片段：

.gitlab-ci.yml

image: docker:latest 
services: 
    - docker:dind 

variables: 
    DOCKER_DRIVER: overlay 

stages: 
    - build 
    - package 
    - deploy 

maven-build: 
    image: maven:3-jdk-8 
    stage: build 
    script: "mvn package -B --settings settings.xml" 
    artifacts: 
    paths: 
     - target/*.jar 

docker-build: 
    stage: package 
    script: 
    - docker build -t gitlab.my.com/group/app . 
    - docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN gitlab.my.com/group/app 
    - docker push gitlab.my.com/group/app 

config.toml

concurrent = 1 
check_interval = 0 

[[runners]] 
    name = "app" 
    url = "https://gitlab.my.com/ci" 
    token = "xxxxxxxx" 
    executor = "kubernetes" 
    [runners.kubernetes] 
    privileged = true 
    disable_cache = true 

包装阶段日志：

running with gitlab-ci-multi-runner 1.11.1 (a67a225) 
    on app runner (6265c5) 
Using Kubernetes namespace: default 
Using Kubernetes executor with image docker:latest ... 
Waiting for pod default/runner-6265c5-project-4-concurrent-0h9lg9 to be running, status is Pending 
Waiting for pod default/runner-6265c5-project-4-concurrent-0h9lg9 to be running, status is Pending 
Running on runner-6265c5-project-4-concurrent-0h9lg9 via gitlab-runner-3748496643-k31tf... 
Cloning repository... 
Cloning into '/group/app'... 
Checking out 10d5a680 as master... 
Skipping Git submodules setup 
Downloading artifacts for maven-build (61)... 
Downloading artifacts from coordinator... ok  id=61 responseStatus=200 OK token=ciihgfd3W 
$ docker build -t gitlab.my.com/group/app . 
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? 
ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 

我在做什么错？

Answer 1

不需要使用：

DOCKER_DRIVER: overlay 

原因好像是不支持叠加，所以SVC-0容器无法开始使用它：

$ kubectl logs -f `kubectl get pod |awk '/^runner/{print $1}'` -c svc-0 
time="2017-03-20T11:19:01.954769661Z" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]" 
time="2017-03-20T11:19:01.955720778Z" level=info msg="libcontainerd: new containerd process, pid: 20" 
time="2017-03-20T11:19:02.958659668Z" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded." 

此外，将export DOCKER_HOST="tcp://localhost:2375"添加到码头构建：

docker-build: 
    stage: package 
    script: 
    - export DOCKER_HOST="tcp://localhost:2375" 
    - docker build -t gitlab.my.com/group/app . 
    - docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN gitlab.my.com/group/app 
    - docker push gitlab.my.com/group/app 

Answer 2

使用Kubernetes时，您必须调整您的Build图像以连接Docker引擎。

添加到您的构建图像：

DOCKER_HOST=tcp://localhost:2375 

报价从文档：

运行泊坞窗：DIND也被称为泊坞窗功能于码头工人的形象也 可能的，但遗憾的是需求容器将以特权模式运行。 如果您愿意冒这个风险，那么可能会出现其他问题，乍一看可能不是那么直截了当的 。由于docker守护进程通常在.gitlab-ci.yaml中作为服务启动，因此它将在您的窗格中作为单独的 容器运行。基本上，容器中的容器仅共享分配给他们的 的卷以及他们可以使用本地主机相互访问的IP地址。 /var/run/docker.sock未由docker：dind容器共享，并且docker 默认情况下会尝试使用它。要覆盖它并使客户端使用tcp 联系另一个容器中的docker守护进程，请确保在构建容器的环境变量中包含DOCKER_HOST = tcp：// localhost：2375中的 。

Gitlab-CI on Kubernetes