Build failing thanks to bad Docker URLs

Build Environment
1

I’ve just started to notice my builds are failing due to “unexpected HTTP status: 503 Service Unavailable” in the Spin Up Environment stage.

Build-agent version 0.0.6918-3a2a4e2 (2018-06-22T13:50:16+0000)
Starting container circleci/node
  image is cached as circleci/node, but refreshing...

  Error pulling image circleci/node: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable... retrying
  image is cached as circleci/node, but refreshing...

  Error pulling image circleci/node: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable... retrying
  image is cached as circleci/node, but refreshing...

  Error pulling image circleci/node: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable... retrying
  image is cached as circleci/node, but refreshing...

  Error pulling image circleci/node: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable... retrying
  image is cached as circleci/node, but refreshing...

  Error pulling image circleci/node: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable... retrying
  image is cached as circleci/node, but refreshing...

Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest: received unexpected HTTP status: 503 Service Unavailable
2

Looks like a Docker Hub problem (i.e. outside of the CircleCI infrastructure). I just did this locally:

docker pull circleci/node
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/latest:
received unexpected HTTP status: 503 Service Unavailable

I also tried a non-CircleCI image, and got the same. Check Docker Hub’s Twitter? I found this status page but it says everything’s OK.

3

Yup, a page of complaints, in Twitter search. :smirk_cat:

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.