Sudden Docker Hub abuse rate limiting without traffic increase

[Al3169]

We started hitting Docker Hub abuse rate limits last week without any increase in traffic. We suspect a change in rate-limiting behavior. Can you confirm whether our IP/subnet is being throttled?

We are getting: 429 Too Many Requests every time we pull an image from docker hub. This has been happening for almost two weeks.

Thanks for any help/advice you can share.

[github-actions]

Thank you for your feedback 👍.

Our team will review your issue shortly.
In the meantime, feel free to provide as many details as possible, as this will speed up the resolution.

If you need assistance rather than providing feedback, please contact the Docker support team via https://hub.docker.com/support/contact for a prompt response, and close this issue.

[lucadruda]

Hi, could you give us more details? What are the images you are trying to pull and what is the username used to pull?

[Al3169]

Hi @lucadruda this is the context. In Harbor we configured the docker hub registry to allow traffic from that hub to harbor. Suddenly, the docker hub started to respond with 429 Too Many Requests. Even if we haven't done any pull of any image from docker hub. We investigated this and found the rate-limit usage https://docs.docker.com/docker-hub/usage/#abuse-rate-limit. However, our pulls won't be exceeding at least 100 in less than 1 minute, according to, our logs.

Therefore, I reach out to the community here to see what are the workarounds available or if there was a recent change in that policy of docker. Because, this is happening with all the images coming from that upstream.

[Al3169]

About the username to pull is one provided in randomly format to each user and that isn't affected by the behavior I described in previous comments.

[Al3169]

Even me with admin privileges I was getting that error message 429 Too Many Requests when doing a pull from Ubuntu and not even a Pipeline.