Docker Hub Registry is down
21–30 of 35 posts
Re: Docker Hub Registry is down
#22It 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?
yeah there's a variety of "free at point of use" services driving the Internet and, sooner or later it seems likely there will need to be a change in how they're funded. It's not just Docker hub, there's services like the various Programming language package repos (npm, rubygems etc) and the Linux distro package repos. I would have had Github in that category, but now it's owned by MS, presumably they don't have many…
Re: Docker Hub Registry is down
#23It 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?
You use VC money and run at a loss while focusing on marketing and tech evangelism, getting more and more startups and hopefully established companies using your software. As the cracks begin to show those growing organizations have too much tied to your system and they can't afford outages and need to scale. So they pay you for the Enterprise version of your software where you actually fix all of flaws present in the community version.
Look at MongoDB if you need a good case study. It was incredibly hyped from about 2009-2015, people would defend it in heated online arguments, and today it's rarely considered for greenfield projects. But they're making about $100M/qtr selling subscriptions to Enterprise & Atlas servicing the technical debt established during that hype cycle.
Re: Docker Hub Registry is down
#24So 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.
Whenever one of our essential 3rd party services go down, I can only shrug and hope they figure it out quickly. They provide a good service and nobody has 100% uptime. Still better than solving it internally, which is even more likely to have downtime. Partial failure is just fact of life. If this is a major issue for your process, it might be better to try and find ways to alter your process so this isn't an issue.…
Being honest no build is worth losing sleep over. We are piggybacking on their service and bandwidth. For us to start building the infrastructure to cache their images doesn't make financial sense, we deploy daily and their uptime always allows for that.
Re: Docker Hub Registry is down
#25So 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.
Re: Docker Hub Registry is down
#26Regular 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).
Re: Docker Hub Registry is down
#27What's the best way around this kind of outage?
1) You can run your own pull-through cache[0] 2) You can use a different registry 3) Run something like kraken[1] so machines can share already-downloaded images with eachother 4) If you need an emergency response, you can docker save[2] an image on a box that has it cached and manually distribute it/load it into other boxes 0: https://docs.docker.com/registry/recipes/mirror/ 1: https://github.com/uber/kraken 2: http…
I'd also add as an option - https://goharbor.io
Re: Docker Hub Registry is down
#28Re: Docker Hub Registry is down
#29Regular 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).
Being paranoid helps. My pipelines never pull images from the hub, I always store those locally.