Docker Hub Registry timming out | Hacker News Reader

Docker Hub Registry timming out

dockerstatus.com

25 pointsvlugorilla13 comments

The elephant in the room here is that so many of us rely on docker's registry, but who's paying for its upkeep and infra? Docker themselves?

It's not like Github which is owned by a trillion dollar company.

I don't know what Docker's revenue is but seems like a bigger risk than GitHub (which people often mention).

Unless this is a solved problem and Docker gets its registry infra for free or paid for by the Linux Foundation or something.

(Before anyone says, just pay for it, we don't REALLY rely on the registry, we as a company use AWS ECR, it's just that some of our build processes rely on it, so it's more like an open source ecosystem relying on it issue)

it's just that some of our build processes rely on it, so it's more like an open source ecosystem relying on it issue

Until your project changes it, you do rely on it, and use their resources.

Changes what? The fact that we use an elixir alpine image that they (hex.pm) host on the docker registry? Doesn’t that mean hex.pm would pay them?

I’m saying we don’t host any of our images. We aren’t a direct customer.

I’m not talking about the image. I’m talking about the hosting!

They have updated their licensing since 2 years ago and a lot of companies (I'm working with) are paying to use it

Ref: https://www.docker.com/pricing/

Seems to coincide with the networking issues in AWS us-east-1. https://health.aws.amazon.com/health/status

At that point, outages in us-east-1 should be a meme in itself.

Dammit Tim!

Sorry.

Same. I also noticed lots of reports here: https://downdetector.com/status/docker/ (though downdetector.com is not an authoritative source, it's been useful to me for seeing if others are experiencing issues)

Thought I was going a little crazy there. I can see it started just over an hour ago.

If you’re relying on an external registry that you’re not paying for, other than the initial pull, you’ve only got yourself to blame.

Yup, experiencing the same here, it even managed to fuck up our Nexus proxy somehow.

Reply on news.ycombinator.com