kubernetes/minikube

integration tests: detect and Log Docker Hub Rate limit Failures

Open

#21442 opened on Aug 27, 2025

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (31,799 stars) (5,222 forks)batch import
help wanted

Description

it should Log something simple instead of we search through logs for the docker rate limit

Example this Gopogh Report https://storage.googleapis.com/minikube-builds/logs/21439/41161/Docker_Linux_containerd.html

Warning  Failed     7m14s (x2 over 7m57s)   kubelet            Failed to pull image "docker.io/nginx:alpine": failed to pull and unpack image "docker.io/library/nginx:alpine": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/nginx/manifests/sha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit

also there is probably a WAY to check how many Docker API calls we have left before Banned, so we can log that in the beggninign of the test and potentially even Wait for it before running the test and wassting time

Contributor guide

Tech stack
dockerkubernetesgo
Domain
testinginfrastructuredevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingDockerminikube testing frameworkDocker Hub API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the minikube integration test framework, specifically how Docker images are pulled in tests (likely in the test utilities). The issue references a Gopogh report; locate the relevant test code that triggers Docker pulls. Explore Docker Hub API endpoints like 'https://auth.docker.io/token' or 'https://registry 1.docker.io/v2/' to check rate limit status. Consider adding a function that calls the Docker Hub API to get current rate limit usage before running tests. Review existing CI scripts for potential integration.