Docker Hub Registry is down

Ugh there goes all our CI stuff.

The specific URL of the incident is the following, but I cannot edit the submission.

https://status.docker.com/pages/incident/533c6539221ae15e3f0...

Congrats! The perfect time to improve your process to remove Docker Hub as a dependency. Embrace the chaos.

A registry cache usually suffices too. It can catch normal executions and can reduce the amount of affected services

At the time that you made your comment, I think it had the potential to be accurate for a lot more people because at that time my understanding is that the outage was ongoing.

With the incident now resolved, I have the benefit of hindsight to say it was down for a total of two hours, which is well within error budget to maintain 99.5% monthly uptime, and since this isn't part of a larger pattern (so far), they're within budget for 99.95% yearly.

I think that for most companies that aren't already heavily invested in a highly available container runtime platform, the cost of this kind of downtime will be less than the cost of self-hosting something better. Especially if they're not in a situation where registry downtime implies an equal amount of customer-facing service downtime.