Skip to content

integration tests: detect and Log Docker Hub Rate limit Failures #21442

@medyagh

Description

@medyagh

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

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions