5 ms·
Docker Is Having an Outage
- agartner 2y agoYep I'm getting 503's. But the status page says nothing is wrong: https://www.dockerstatus.com/ 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-dockerhub-images https://cloud.google.com/artifact-registry/docs/pull-cached-...
- singlow 2y agoSame here - checked from multiple locations.
- bgschulman31 2y agoSame here. 503 when we try to pull an image during our deployment pipeline.
- kulor 2y ago"Full Service Disruption" for Docker Hub Registry acknowledged at the time of writing
- evil-olive 2y agoas 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/ https://registry.docker.io/` on 2 CI boxes in 2 different datacenters.
- josh-sematic 2y agoYup, getting: `Error response from daemon: Get "https://registry-1.docker.io/v2/ https://registry-1.docker.io/v2/": received unexpected HTTP status: 503 Service Unavailable`
- greggsy 2y agoI had the same exact message two days ago, but I chalked it up to a DNS issue on my end.
- rated 2y agoCan 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 2y agoThat’s why we mirror and scan the images with Artifactory. Prevents these issues
- hipadev23 2y agoDoes 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 2y agoIf 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
- hipadev23 2y agoyou rock, thank you.
- mhio 2y agodocker build --pull=false ...
- hipadev23 2y agoit’s not the pull, it’s a metadata check
- mhio 2y agoThe metadata check is part of the builds image pull process. The step can resolve a `FROM repo/image:tag` reference to the content sha the tag points to, and then if required fetch the content. In any case, recent-ish (maybe 24+) versions of docker default to a "prefer local" mode in buildkit so a local cached entry will be returned first if possible before any remotes are resolved. Out of interest, what docker/buildx/buildkit versions were attempting the connection? We ran into this on some container builds that run offline last year some time and I'm wondering if it was due to some ancient docker, as that flag appears useless on current docker. - https://github.com/docker/buildx/blob/7b1ec7211d871dfba53b10f0c7cf846022665aa5/build/opt.go#L282-L287 https://github.com/docker/buildx/blob/7b1ec7211d871dfba53b10...
- JSDevOps 2y agoProbably linked to the Cloudflare outage.
- dzddd 2y agoDocker is back up.
- apantel 2y agoSomething wasn’t run in a container…
- mococa 2y agoI am using orbstack, best alternative to docker.
- paranoidrobot 2y agoIt'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.
- pacavaca 2y agoWelp, I guess I'm calling it a day off
- gavmor 2y agoYou mean the "Docker Hub Registry" is having an outage.
- hervem 2y agoThey surely tried to release the "V3-beta not beta"... Or the 2.9 which is a pre V3-beta xD
- hn92726819 2y agoDocker means 4 things: https://news.ycombinator.com/item?id=37335945 https://news.ycombinator.com/item?id=37335945
- deleted 2y ago[deleted]
- kachapopopow 2y agoThis 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).
- deleted 2y ago[deleted]