Docker Hub Is Down
11–20 of 110 posts
Re: Docker Hub Is Down
#12Re: Docker Hub Is Down
#13Earlier quoted context omitted.
I guess the best way would be to have a self-hosted pull-through registry with a cache. This way you'd have all required images ready even when dockerhub is offline. Unfortunately that does not help in an outage because you cannot fill the cache now.
In the case where you still have an image locally, trying to build will fail with an error complaining about not being able to load metadata for the image because a HEAD request failed. So, the real question is, why isn't there a way to disable the HEAD request for loading metadata for images? Perhaps there's a way and I don't know it.
Re: Docker Hub Is Down
#14Dupe https://news.ycombinator.com/item?id=45366942
Re: Docker Hub Is Down
#15Also, isn't it weird that it takes so long to fix given the magnitude of the issue? Already down for 3 hours.
Re: Docker Hub Is Down
#16Re: Docker Hub Is Down
#17I can see an image tag available in the cache in my project on cloud.google.com, but after attempting to pull from the cache (and failing) the image is deleted from GAR :(
Re: Docker Hub Is Down
#18I didn't even really realize it was a SPOF in my deploy chain. I figured at least most of it would be cached locally. Nope, can't deploy. I don't work on mission-critical software (nor do I have anyone to answer to) so it's not the end of the world, but has me wondering what my alternate deployment routes are. Is there a mirror registry with all the same basic images? (node/alpine) I suppose the fact that I didn't no…
I guess the best way would be to have a self-hosted pull-through registry with a cache. This way you'd have all required images ready even when dockerhub is offline. Unfortunately that does not help in an outage because you cannot fill the cache now.
docker image ls
docker tag name/name:version your.registry/here/name/name:version
docker push your.registry/here/name/name:version