3 ms·
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 off
by tom1337 1y ago
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.
- pebble 1y agoThis is the way tho this can lead to fun moments like I was just setting up a new cluster and couldn't figure out why I was having problems pulling images when the other clusters were pulling just fine. Took me a while to think of checking the docker hub status page.
- cipherself 1y agoIn 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.
- switz 1y agoYeah, this is the actual error that I'm running into. Metadata pages are returning 401 and bailing out of the build.
- Too 1y agoSure? --pull=missing should be the default.
- cipherself 1y agoWhile I haven’t tried --pull=missing, I have tried --pull=never, which I assume is a stricter version and it was still attempting the HEAD request.
- tln 1y agoYou 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