integration tests: detect and Log Docker Hub Rate limit Failures · kubernetes/minikube#21442

(3 评论) (0 反应) (1 负责人)Go (31,799 star) (5,222 fork)batch import

help wanted

描述

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

贡献者指南

技术栈: dockerkubernetesgo
领域: testinginfrastructuredevops
议题类型: feature
难度: 3
预计时间: 1-2 days
活动状态: active
清晰度: mostly clear
前置要求: Go programmingDockerminikube testing frameworkDocker Hub API
新手友好度: 40
研究方向: 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.