我正在尝试使用以下.gitlab-ci.yml
文件实现GitLab持续集成(CI)管道:
image: docker:latest
# When using dind, it's wise to use the overlayfs driver for
# improved performance.
variables:
DOCKER_DRIVER: overlay
services:
- docker:dind
before_script:
- docker info
- curl -L "https://github.com/docker/compose/releases/download/1.10.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
- chmod +x /usr/local/bin/docker-compose
- export PATH=/usr/local/bin:$PATH
- echo $PATH
stages:
- build
- test
build:
stage: build
script:
- docker-compose build
- docker-compose up -d
test:
stage: test
script:
- cd tests/tester
- pytest test_run_tester.py
except:
- /^.*skip_tests$/
但是,在GitLab中我收到以下错误消息:
Running with gitlab-ci-multi-runner 1.10.4 (b32125f)
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Waiting for services to be up and running...
Pulling docker image docker:latest ...
Running on runner-2e54fd37-project-13-concurrent-0 via scw-de9c9c...
Fetching changes...
HEAD is now at 2504a08 Update CI config
From https://lab.iperlane.com/gio/ipercron-compose
2504a08..5c2f23f CI -> origin/CI
Checking out 5c2f23f1 as CI...
Skipping Git submodules setup
$ docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.13.1
Storage Driver: overlay
Backing Filesystem: extfs
Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.8.14-docker-2
Operating System: Alpine Linux v3.5 (containerized)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.751 GiB
Name: 90395a030c02
ID: 7TKR:5PQN:XLFM:EJST:NF2V:NLQC:I2IZ:6OZG:TR4U:ZEAK:EVXE:HIF7
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
$ curl -L "https://github.com/docker/compose/releases/download/1.10.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 600 0 600 0 0 1175 0 --:--:-- --:--:-- --:--:-- 1176
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
3 7929k 3 254k 0 0 116k 0 0:01:08 0:00:02 0:01:06 258k
17 7929k 17 1358k 0 0 433k 0 0:00:18 0:00:03 0:00:15 704k
61 7929k 61 4861k 0 0 1164k 0 0:00:06 0:00:04 0:00:02 1636k
100 7929k 100 7929k 0 0 1703k 0 0:00:04 0:00:04 --:--:-- 2300k
$ chmod +x /usr/local/bin/docker-compose
$ export PATH=/usr/local/bin:$PATH
$ docker-compose build
/bin/sh: eval: line 51: docker-compose: not found
ERROR: Build failed: exit code 127
系统似乎无法找到docker-compose
,即使在安装它并将其添加到路径之后也是如此。是否可能有其他图像可以制作docker-compose
命令,或者在.gitlab-ci.yml
中安装它的方式不同?
答案 0 :(得分:10)
这是一个复杂的问题。
docker:latest
图片基于alpine
(Alpine Linux),使用musl-libc
构建。这个系统是非常准确的,因此没有一个完整的桌面Linux可能拥有的一切。实际上,需要专门为此系统编译动态可执行文件。
docker-compose
是一个Python应用程序,使用PyInstaller捆绑到Linux可执行文件中。这些可执行文件实际上只能在它们构建的系统上运行。如果您运行alpine
容器和apk add file
,则可以看到您下载的(动态链接)可执行文件需要特定的解释器。
# file /usr/local/bin/docker-compose
/usr/local/bin/docker-compose.pyinstaller: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=00747fe5bcde089bb4c2f1ba7ab5348bc02ac5bf, stripped
/lib64/ld-linux-x86-64.so.2
中不存在alpine
问题。事实上,/lib64
甚至不存在。
因为docker-compose
是Python应用程序,所以can also be installed using pip
:
在alpine
容器内进行测试:
$ docker run --rm -it alpine /bin/bash
以下是您可以手动运行或添加到.gitlab-ci.yml
before_script
的命令:
# apk add --no-cache python py2-pip
...
# pip install --no-cache-dir docker-compose
...
# docker-compose -v
docker-compose version 1.11.1, build 7c5d5e4
事实证明,实际上存在一个悬而未决的问题:
答案 1 :(得分:1)
Docker-compose现在是正式映像。你可以放
image:
name: docker/compose:1.23.2
entrypoint: [""]
在您的.gitlab-ci.yml
顶部的。您需要删除组成图像的默认入口点,这是由第二行完成的。之后,您可以同时使用docker
和docker-compose
。
这符合GitLab 9.4的要求。您还可以构建自定义图片
FROM docker/compose:1.23.2
ENTRYPOINT []
并将其用作您的图片。