Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker Hub Is Down

dockerstatus.com

Post reply on HN
Print view View original

51–60 of 110 posts

Re: Docker Hub Is Down

#52

Post by andrewstuart2 »

__turbobrew__ wrote: post #45

Anyone have recommendations for an image cache? Native kubernetes a plus. What would be really nice is a system with mutating admission webhooks for pods which kicks off a job to mirror the image to a local registry and then replaces the image reference with the mirrored location.

CNCF has harbor [0], which I use at home and have deployed in a few clusters at work, and it works well as a pull through cache. In /etc/containers/registries.conf it's just another line below any registry you want mirrored.

    [[registry]]
    location = "docker.io"
    [[registry.mirror]]
    location = "core.yourharbor.example.com/hub"
Where hub is the name of the proxy you configured for, in this case, docker.io. It's not quite what you're asking for but it can definitely be transparent to users. I think the bonus is that if you look at a podspec it's obvious where the image originates and you can pull it yourself on your machine, versus if you've mutated the podspec, you have to rely on convention.

[0] https://goharbor.io/

Re: Docker Hub Is Down

#53

Post by cyberax »

viraptor wrote: post #44
cyberax wrote: post #27

Earlier quoted context omitted.

Quay.io is nice (but you have to memorize the spelling of its name)

Or start a pronunciation revolution and say "kway". It's all made up anyway ;-)

It _is_ pronounced "kway", and it _is_ a real word: https://www.merriam-webster.com/dictionary/quay !

Re: Docker Hub Is Down

#54

Post by sublinear »

Somewhat unrelated, but GitLab put out a blog post earlier this year warning users about Docker Hub's rate limiting: https://about.gitlab.com/blog/prepare-now-docker-hub-rate-li...

We chose to move to GitLab's container registry for all the images we use. It's pretty easy to do and I'm glad we did. We used to only use it for our own builds.

The package registry is also nice. I only wish they would get out of the "experimental" status for apt mirror support.

Re: Docker Hub Is Down

#56

Post by gnabgib »

cyberax wrote: post #53
viraptor wrote: post #44

Earlier quoted context omitted.

Or start a pronunciation revolution and say "kway". It's all made up anyway ;-)

It _is_ pronounced "kway", and it _is_ a real word: https://www.merriam-webster.com/dictionary/quay !

It's pronounced keɪ (from your link - The spelling quay, first appearing in the sixteenth century, follows modern French. As noted by the Oxford English Dictionary, third edition, the expected outcome of Middle English keye would be /keɪ/ in Modern English). Or key (with modern spelling).

Re: Docker Hub Is Down

#58

Post by pm90 »

esafak wrote: post #38

What's the easiest way to cache registries like docker, pypi, and npm these days?

Someone mentioned Artifactory; but its honestly not needed. I would very highly recommend an architecture where you build everything into a docker image and push it to an internal container registry (like ecr; all public clouds have one) for all production deployments. This way, outages only affect your build/deploy pipeline.

Re: Docker Hub Is Down

#60

Post by GuinansEyebrows »

paulddraper wrote: post #46
viraptor wrote: post #41

Earlier quoted context omitted.

You pull the images you want to use, preferably with some automated process, then push them to your own repo. And anyways use your own repo when pulling for dev/production. It saves you from images disappearing as well.

What do you like using for your own repo? Artifactory? Something else?

I have experience with ECR. If you’re in the AWS ecosystem it does the job.
Post reply on HN