top | item 40743975

Docker Is Having an Outage

62 points| cuuupid | 1 year ago |downdetector.com | reply

28 comments

order
[+] agartner|1 year ago|reply
Yep I'm getting 503's. But the status page says nothing is wrong: https://www.dockerstatus.com/

Update: I configured the gcp docker mirror and can pull images again https://cloud.google.com/artifact-registry/docs/pull-cached-...

[+] bgschulman31|1 year ago|reply
Same here. 503 when we try to pull an image during our deployment pipeline.
[+] kulor|1 year ago|reply
"Full Service Disruption" for Docker Hub Registry acknowledged at the time of writing
[+] singlow|1 year ago|reply
Same here - checked from multiple locations.
[+] evil-olive|1 year ago|reply
as of 22:45 UTC (~30 minutes ago) they marked the status green with "Issue is mitigated, monitoring the situation"

...but I'm still getting 503 responses on my dev box as well as when I run `curl https://registry.docker.io/` on 2 CI boxes in 2 different datacenters.

[+] hipadev23|1 year ago|reply
Does anyone know how to skip/bypass the "load metadata for docker.io/" step on a build? I already have the image cached but it fails on that step regardless.
[+] shykes|1 year ago|reply
If you specify the image digest in the image address, buildkit (the low-level implementation of docker build) will skip the metadata lookup.

For example:

  FROM nginx:1.21.6@sha256:ec5c36ef5a2c29cf90d5b59c5f9f90272b472c604983b474b201bc2bfa123e6f
[+] mhio|1 year ago|reply

    docker build --pull=false ...
[+] kachapopopow|1 year ago|reply
This is the 2nd one this year I'm pretty sure. I wonder what the losses come out to all things considered in terms of development time and applications going offline (claude was offline for 10 or so minutes when this happened).
[+] pacavaca|1 year ago|reply
Welp, I guess I'm calling it a day off
[+] rated|1 year ago|reply
Can also confirm that our entire pipeline is down. We use CircleCI and henceforth all deployments are instantly failing. Luckily no mission critical deployments today...
[+] firesteelrain|1 year ago|reply
That’s why we mirror and scan the images with Artifactory. Prevents these issues
[+] dzddd|1 year ago|reply
Docker is back up.
[+] JSDevOps|1 year ago|reply
Probably linked to the Cloudflare outage.
[+] rated|1 year ago|reply
I don't see any outage on CF's side besides something will billing and some normal maintenance, where do you see it?
[+] delduca|1 year ago|reply
I am using orbstack, best alternative to docker.
[+] paranoidrobot|1 year ago|reply
It's not clear how this would help with a dockerhub outage. It doesn't appear to offer a pull-through cache?

The reason the outage is impactful on many is because they're using containers which are hosted on dockerhub.

[+] apantel|1 year ago|reply
Something wasn’t run in a container…