Fixing Docker Hub Rate Limiting Errors in CI/CD Pipelines

Add Docker Hub Credentials and Prosper. AWS CodeBuild Instructions Included.

Edoardo Nosotti
RockedScience

--

Photo by Matthew Cooksey on Unsplash

In an effort to leave its troubled recent past behind, Docker has significantly revamped its business model over the course of this (very troubled indeed) year. As a part of this renovation, back in August the company announced big changes to the Docker Hub service too. Effective November 1, 2020:

  • Stale (inactive for ≥6 months) images on the Docker Hub will be purged
  • Pulls will be rate limited for anonymous users and free accounts

We should all know by now that there are no such things as unlimited services, capacity or vacations in the real world. Even huge companies faltered and crumbled under the burden of “unlimited” paid services. How is Docker supposed to pay for 4.5 petabytes of free storage for inactive images?

So I totally understand Docker’s change of course. Also, dealing with clear and predictable usage limits is easier than handling uncertainty.

In spite of the assurances given by the Docker team, many CI/CD pipelines will be impacted, especially if built on SaaS/PaaS solutions. Also, it looks like some limits are being enforced well before the November 1 deadline. It’s September…

--

--

Edoardo Nosotti
RockedScience

Certified Cybersecurity Analyst and Senior Cloud Solutions Architect. Passionate about IoT, AI, ML and automation.