nll*_*dfx 6 continuous-integration gitlab docker gitlab-ci gitlab-ci-runner
我正在尝试使用 gitlab ci feature 构建我的项目。根据这个问题,我已经正确地完成了一切。这是我的 .gitlab-ci.yml。
.gitlab-ci.yml
image: docker:latest
services:
- docker:dind
stages:
- build
- release
- deploy
variables:
DOCKER_DRIVER: overlay
MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode"
cache:
paths:
- .m2/repository/
- auth/target/
before_script:
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
build:
image: maven:latest
stage: build
script:
- mvn $MAVEN_CLI_OPTS package
auth-release:
stage: release
when: on_success
script:
- docker build -f auth/Dockerfile -t "$CI_REGISTRY/$CI_PROJECT_PATH/auth" ./auth
- docker push "$CI_REGISTRY/$CI_PROJECT_PATH/auth"
Run Code Online (Sandbox Code Playgroud)
但控制台打印出错误:
控制台输出
Running with gitlab-runner 11.7.0-rc1 (6e20bd76)
on docker-auto-scale ed2dce3a
Using Docker executor with image maven:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:067814781fbba30c17a86aa6159516660b6c210485ac9ac346d5101d6e4b70f0 for docker:dind ...
Waiting for services to be up and running...
Pulling docker image maven:latest ...
Using docker image sha256:3bc97dc2e7ba13887f5a850968419ad0e83fc482acd1cf0d9606882b665e39f3 for maven:latest ...
Running on runner-ed2dce3a-project-10090201-concurrent-0 via runner-ed2dce3a-srm-1547629674-aa23c547...
Cloning repository...
Checking out 10c9202f as master...
Skipping Git submodules setup
Checking cache for default...
FATAL: file does not exist
Failed to extract cache
$ docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
/bin/bash: line 76: docker: command not found
ERROR: Job failed: exit code 1
Run Code Online (Sandbox Code Playgroud)
我究竟做错了什么?
你混淆了你的构建阶段。
根据您的日志,您在build舞台上失败,这是使用maven:latest图像执行的,正如您的yaml.
但你也有你的before_script:
before_script:
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
Run Code Online (Sandbox Code Playgroud)
因此,该脚本尝试在图像上执行maven并失败,因为maven图像没有内部docker。也许,您只想执行您的before_script唯一 forauth-release阶段 - 它将在那里工作,因为auth-release使用docker:latest图像,而图像又包含docker可执行文件。
您可能对您的docker:dind服务感到困惑,认为它会docker在所有映像中为您提供 CLI - 这是行不通的。docker:dind服务为您提供了docker守护进程,但您仍然需要docker在所有映像中安装 CLI 才能与服务交互。
| 归档时间: |
|
| 查看次数: |
7158 次 |
| 最近记录: |