container image not usable because of docker hub rate limits

[ibotty]

Describe the bug

I cannot run go-neb on my on-prem kubernetes cluster:

Internal error occurred: docker.io/matrixdotorg/go-neb:latest: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

I would propose publishing the image on a registry without draconian rate limits, e.g. quay.io or github's own registry.

To Reproduce
Steps to reproduce the behavior:

1. Use docker hub without account often (e.g. skopeo inspect docker://matrixdotorg/go-neb > /dev/null for 500 times),
2. get rate limited
3. See error

Expected behavior
It works.

[t3chguy]

go-neb follows the rest of matrix-org namespace projects in using dockerhub - if you want to workaround the ratelimit in your k8s use https://medium.com/rossum/how-to-overcome-docker-hub-pull-limits-in-a-kubernetes-cluster-382f317accc1#:~:text=The%20limit%20is%20100%20pulls,Kubernetes%20clusters%20are%20running%20smoothly.

[ibotty]

This won't change anything, we do have a big cluster running behind a single IP. Checking if there is a new image does count against the rate limit and this adds up. Please reconsider.

[t3chguy]

It is not within this project's remit to veer away from the standard repository that matrix-org uses, this won't get any movement here but not sure what repo would be better