Quick fix for the newly introduced Docker Hub rate limits
Docker implemented new pull rate limits to Docker Hub starting April 1st, which may significantly impact CI/CD pipelines across the industry, including those running on GitLab. The most significant change is the 100 pulls-per-6-hours limit for unauthenticated users.
GitLab explains the impact of these changes on CI/CD pipelines in their blog post.
The Adfinis Solution
To mitigate the problems that arise from this change, Adfinis has prepared a quick fix offering by providing a Docker-mirror solution to cache images. This avoids the rate limit and the requirement to solve the problem individually for every developer.
The set rate limit might not be reached during regular operation, but there are various scenarios where many images must be pulled simultaneously. This may lead to an outage due to the rate limit. It’s better to take precautions now than deal with disruptions later.
Options
Option 1: A Linux Virtual Machine with internet access that can run Docker containers using Docker Compose or Postman and has enough storage to cache images.
Option 2: A Kubernetes environment with internet access and enough storage to cache images.
We provide an Ansible Playbook or a Helm Chart to deploy the solution.
Requirement: A Docker Hub subscription is required so the mirror can authenticate to Docker Hub.
Approach and Offering
Prepare
Pre-sales call to discuss the impact and agree on the needed solution based on the two options above. (1 - 2 hours)
Implement
Implementing the solution by providing the necessary configuration and support to integrate it into GitLab Pipelines, ensuring the mirror is automatically used by all pipelines that require access to Docker Hub.
Pricing
The complexity of the target environment will determine the time required to deploy the solution. We estimate 0.5 to 2 days.
Get In Touch
