Docker Hub Is Down
31–40 of 110 posts
Re: Docker Hub Is Down
#32Earlier 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.
You might still have it on your dev box or build box docker image ls docker tag name/name:version your.registry/here/name/name:version docker push your.registry/here/name/name:version
Re: Docker Hub Is Down
#33I 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…
It's a bit stupid that I can't restart (on Coolify) my container, because pulling the image fails, even though I am already running it, so I do have the image, I just need to restart the Node.js process...
Re: Docker Hub Is Down
#34Earlier quoted context omitted.
Basically all my Docker images were being built from Github repos anyways, so I just switched to Github's container registry.
GHCR authentication is just broken. They still require the deprecated personal access tokens.
Re: Docker Hub Is Down
#35I was hoping google cloud artifact registry pull-thru caching would help. Alas, it does not. I 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
#36Re: Docker Hub Is Down
#37Re: Docker Hub Is Down
#38Re: Docker Hub Is Down
#39So that's why. This gave me the kick I needed to finally switch over the remaining builds to the pull-through cache.