503 Dockerhub

Feedback & Bug Reports
#1

Dear Circleci,

We suddenly get the following issue in our deploys. It has something to do with docker-hub? How can we prevent this in the future and when will this be fixed?

Build-agent version 0.1.900-892a9f73 (2018-10-25T15:49:42+0000)
Starting container circleci/node:9.10
  image cache not found on this host, downloading circleci/node:9.10

  Error pulling image circleci/node:9.10: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable... retrying
  image cache not found on this host, downloading circleci/node:9.10

  Error pulling image circleci/node:9.10: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable... retrying
  image cache not found on this host, downloading circleci/node:9.10

  Error pulling image circleci/node:9.10: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable... retrying
  image cache not found on this host, downloading circleci/node:9.10

  Error pulling image circleci/node:9.10: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable... retrying
  image cache not found on this host, downloading circleci/node:9.10

  Error pulling image circleci/node:9.10: Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable... retrying
  image cache not found on this host, downloading circleci/node:9.10

Error response from daemon: Get https://registry-1.docker.io/v2/circleci/node/manifests/9.10: received unexpected HTTP status: 503 Service Unavailable
Issue with spinning up environment
#2

Hi there,

We are also getting the same with the 2.4.2-node-browsers image.

Build-agent version 0.1.900-892a9f73 (2018-10-25T15:49:42+0000)
Starting container circleci/ruby:2.4.2-node-browsers
 image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error pulling image circleci/ruby:2.4.2-node-browsers: Error response from daemon: Get https://registry- 
1.docker.io/v2/circleci/ruby/manifests/2.4.2-node-browsers: received unexpected HTTP status: 503 
Service Unavailable... retrying
  image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error pulling image circleci/ruby:2.4.2-node-browsers: Error response from daemon: Get https://registry- 
1.docker.io/v2/circleci/ruby/manifests/2.4.2-node-browsers: received unexpected HTTP status: 503  
Service Unavailable... retrying
image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error pulling image circleci/ruby:2.4.2-node-browsers: Error response from daemon: Get https://registry- 
1.docker.io/v2/circleci/ruby/manifests/2.4.2-node-browsers: received unexpected HTTP status: 503 
Service Unavailable... retrying
image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error pulling image circleci/ruby:2.4.2-node-browsers: Error response from daemon: Get https://registry- 
1.docker.io/v2/circleci/ruby/manifests/2.4.2-node-browsers: received unexpected HTTP status: 503 
Service Unavailable... retrying
 image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error pulling image circleci/ruby:2.4.2-node-browsers: Error response from daemon: Get https://registry- 
1.docker.io/v2/circleci/ruby/manifests/2.4.2-node-browsers: received unexpected HTTP status: 503 
Service Unavailable... retrying
image cache not found on this host, downloading circleci/ruby:2.4.2-node-browsers

Error response from daemon: Get https://registry-1.docker.io/v2/circleci/ruby/manifests/2.4.2-node- browsers: received unexpected HTTP status: 503 Service Unavailable
#3

Okay, looks like I got one working now.
There is an announcement banner up about DockerHub issues

#4

This is working for me now, it was throwing 503’s like above ~10mins ago.

#5

It seems they removed th 9.10 image… I switched to 8.12 which was available

#6

I also met this problem, it was DockerHub side and resolved now.

#7

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