Publish container image to registry without draconian rate limits e.g. quay.io #1379

New Issue

OVERLORD · 2025-10-09T17:13:16+03:00

OVERLORD commented

2025-10-09 17:13:16 +03:00

Originally created by @ibotty on GitHub.

Subject of the issue

It would be great to deploy to a container registry that does not rate limit image pulls (and checks for new image tags). It's possible to apply to dockerhub to be exempt, but that comes with many strings attached (advertising from docker with your image, etc.). I happen to like quay.io as a registry that does not limit pulls (except for abuse) and comes with a free account.

I get the following errors.

error: Import failed (InternalError): Internal error occurred: docker.io/vaultwarden/server: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

Deployment environment

Install method:
Not yet. Should be kubernetes.

Steps to reproduce

podman pull docker.io/vaultwarden/server:latest too many times.

Expected behaviour

podman pull succeeds.

Actual behaviour

docker.io/vaultwarden/server: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

Originally created by @ibotty on GitHub. ### Subject of the issue It would be great to deploy to a container registry that does not rate limit image pulls (and checks for new image tags). It's possible to apply to dockerhub to be exempt, but that comes with many strings attached (advertising from docker with your image, etc.). I happen to like quay.io as a registry that does not limit pulls (except for abuse) and comes with a free account. I get the following errors. ``` error: Import failed (InternalError): Internal error occurred: docker.io/vaultwarden/server: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 ``` ### Deployment environment * Install method: Not yet. Should be kubernetes. ### Steps to reproduce `podman pull docker.io/vaultwarden/server:latest` too many times. ### Expected behaviour `podman pull` succeeds. ### Actual behaviour > docker.io/vaultwarden/server: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

OVERLORD closed this issue

2025-10-09 17:13:18 +03:00

OVERLORD commented

2025-10-09 17:13:19 +03:00

@nalakawula commented on GitHub:

I use cached docker image as workaround for docker hub rate limit, check this out:
Pulling cached Docker Hub images

@nalakawula commented on GitHub: I use cached docker image as workaround for docker hub rate limit, check this out: [Pulling cached Docker Hub images](https://cloud.google.com/container-registry/docs/pulling-cached-images)

OVERLORD commented

2025-10-09 17:13:19 +03:00

@Felixkruemel commented on GitHub:

GitHub has a registry which it'd be easy to push to as part of CI, and doesn't have rate limits on downloads.

This would be amazing!

@Felixkruemel commented on GitHub: > > > GitHub has a registry which it'd be easy to push to as part of CI, and doesn't have rate limits on downloads. This would be amazing!

OVERLORD commented

2025-10-09 17:13:19 +03:00

@RealOrangeOne commented on GitHub:

GitHub has a registry which it'd be easy to push to as part of CI, and doesn't have rate limits on downloads.

@RealOrangeOne commented on GitHub: GitHub has a registry which it'd be easy to push to as part of CI, and doesn't have rate limits on downloads.

OVERLORD commented

2025-10-09 17:13:20 +03:00

@BlackDex commented on GitHub:

I'm going to move this to the discussions under Ideas, also to keep the issues for actual issues to the software.

@BlackDex commented on GitHub: I'm going to move this to the discussions under `Ideas`, also to keep the issues for actual issues to the software.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1379