A common exception when using DockerHub to pull images is hitting the limit rate of pulls per period. Usually caused by running too many tests/builds during CI.
You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limits
The intention of this article is to cover the most common cases related to reaching the limit of pulls, the idea is to increment it with time.
Case 1 - I’m not using anonymous authentication and I’m still hitting the limit
You are probably using a public URL in your Docker connector, to connect to a private registry, please use the private URL:
- Public: https://registry.hub.docker.com/v2/
- Private: https://index.docker.io/v2/
For more information: Docker Connector Settings Reference | Harness Developer Hub
If you have any suggestions on how to improve this article, or helpful and specific examples of permissions related issues that may be of use to others, please leave a comment with the information as this document is intended to evolve over time.
If this article cannot resolve your issue, don’t hesitate to contact us here: [email protected] – or through the Zendesk portal in Harness SaaS.