GitLab CI错误：准备失败：发布https … docker％3Adind：net / http：超时等待响应头
GitLab CI自过去一小时抛出错误，无法继续。 .gitlab-ci.yml不会改变，而且非常简单（ 如下所示 ）。
只有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
开始工作没有任何修改，也许内部gitlab服务器超载，因此超时错误。
67.205.149是一个DigitalOcean IP地址。
DigitalOcean的状态是绿色的，所以它不直接与平台本身相连。
而这似乎并不是一个GitLab-CI gitlab-workhorse路由器的问题 。
因此，请检查由GitLab使用的DigitalOcean实例上托pipe的Dockerregistry的状态：它（dockerregistry）可能已closures（即使GitLab Status未提及它）。
OP确认情况正是如此。
或者使用私有实例的内置GitLab Dockerregistry 。