GitLab CI ERROR: Preparation failed: Post https...docker%3Adind: net/http: timeout awaiting response headers
GitLab CI ERROR: Preparation failed: Post https...docker%3Adind: net/http: timeout awaiting response headers
GitLab CI 自过去一小时以来抛出错误，无法继续。 .gitlab-ci.yml没有变化，非常简单（如end所示）。
仅 Dockerfile 已更改 - 但系统未启动事件 Dockerfile。有什么补救措施？
错误日志
Running with gitlab-ci-multi-runner 1.9.0 (82714ae)
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://67.205.149.124:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://67.205.141.137:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://192.241.149.44:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
ERROR: Build failed (system failure): Post https://192.241.149.44:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
.gitlab-ci.yml
image: docker:latest
services:
- docker:dind
stages:
- build
variables:
NAMEBRAN: registry.gitlab.com/myusername/project:$CI_BUILD_REF_NAME
NAMELAST: registry.gitlab.com/myusername/project:latest
build_image:
stage: build
script:
#LOGIN
- docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN registry.gitlab.com
#BUILD [NEEDS PUSH TO NAME] WITH NAME = $NAMEBRAN
- docker build -t $NAMEBRAN .
- docker push $NAMEBRAN
#TAG $NAMEBRAN as $NAMELAST
- docker pull $NAMEBRAN
- docker tag $NAMEBRAN $NAMELAST
- docker push $NAMELAST
only:
- dockerbranch
67.205.149 是一个 DigitalOcean IP 地址。
DigitalOcean status是绿色的，所以没有直接链接到平台本身。
而且这好像不是GitLab-CI gitlab-workhorse router issue.
因此请检查托管在 GitLab 使用的 DigitalOcean 实例上的 Docker 注册表的状态：它（docker 注册表）可能已关闭（即使 GitLab Status 没有提及它）。
OP 确认是这种情况。
或者使用私有实例的built-in GitLab Docker registry。
在没有任何修改的情况下开始工作，可能内部 gitlab 服务器超载因此超时错误。
GitLab CI 自过去一小时以来抛出错误，无法继续。 .gitlab-ci.yml没有变化，非常简单（如end所示）。
仅 Dockerfile 已更改 - 但系统未启动事件 Dockerfile。有什么补救措施？
错误日志
Running with gitlab-ci-multi-runner 1.9.0 (82714ae)
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://67.205.149.124:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://67.205.141.137:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Pulling docker image docker:dind ...
ERROR: Preparation failed: Post https://192.241.149.44:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
Will be retried in 3s ...
ERROR: Build failed (system failure): Post https://192.241.149.44:2376/v1.18/images/create?fromImage=docker%3Adind: net/http: timeout awaiting response headers
.gitlab-ci.yml
image: docker:latest
services:
- docker:dind
stages:
- build
variables:
NAMEBRAN: registry.gitlab.com/myusername/project:$CI_BUILD_REF_NAME
NAMELAST: registry.gitlab.com/myusername/project:latest
build_image:
stage: build
script:
#LOGIN
- docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN registry.gitlab.com
#BUILD [NEEDS PUSH TO NAME] WITH NAME = $NAMEBRAN
- docker build -t $NAMEBRAN .
- docker push $NAMEBRAN
#TAG $NAMEBRAN as $NAMELAST
- docker pull $NAMEBRAN
- docker tag $NAMEBRAN $NAMELAST
- docker push $NAMELAST
only:
- dockerbranch
67.205.149 是一个 DigitalOcean IP 地址。
DigitalOcean status是绿色的，所以没有直接链接到平台本身。
而且这好像不是GitLab-CI gitlab-workhorse router issue.
因此请检查托管在 GitLab 使用的 DigitalOcean 实例上的 Docker 注册表的状态：它（docker 注册表）可能已关闭（即使 GitLab Status 没有提及它）。
OP 确认是这种情况。
或者使用私有实例的built-in GitLab Docker registry。
在没有任何修改的情况下开始工作，可能内部 gitlab 服务器超载因此超时错误。