by alpb on 10/15/19, 5:32 PM
Regular reminder that Docker Hub is not really an enterprise registry with an SLA. You should use pretty much anything else for serious applications that rely on pulling images in the hot path (such as auto-scaling up).
by danielecook on 10/15/19, 5:35 PM
It seems like dockerhub requires a lot of bandwidth...lots of people being able to pull gigabytes worth of images everyday. Does anyone know anything behind the economics behind this? How can they offer it for free?
by bluedino on 10/15/19, 5:14 PM
What's the best way around this kind of outage?
by nelsonmarcos on 10/15/19, 6:19 PM
If we only had listened our sysadmin...
by beilabs on 10/15/19, 5:43 PM
So my CI environment requires access to other docker images, all hosted on Docker Hub.
Seems like the tech giants should load balance these images for the good of the Internet to provide some decent redundancy and for my sanity at 11.30pm.
by driverdan on 10/15/19, 5:54 PM
This has broken fresh containerized deploys on Heroku, which is surprising since they run their own registry. They should be proxying Hub, it'd save them a ton of bandwidth.
by popotamonga on 10/15/19, 5:26 PM
What a coincidence, the same minute all my lightsail instances got unresponsive and then 20 minutes stuck on "stopping".
Launched a new one.. docker pull bam error. Customer unsatisfied.
by dpix on 10/15/19, 6:09 PM
Looks like it's back up now, whew!
by bluedino on 10/15/19, 5:25 PM
It went from orange to red.
Incident Status Full Service Disruption
by tekno45 on 10/15/19, 5:07 PM
uuugh. was just about to do some testing
by tryphan on 10/15/19, 5:18 PM
More confidence for the folks at Docker Inc.