minikube Tests fail with "You have reached your unauthenticated pull rate limit"

Looking at many failures for https://github.com/kubernetes/minikube/pull/20720:

We need to pull images from other registry that cannot with rate limit.

In ramen we use quay.io to avoid this. Another solution is local registry running in the CI environment.

We have 2 issues:

Use from the test host: this was mostly fixed by logging to docker.io in the test script
Use inside the guest: this requires providing a pull secret for all namespaces, or hopefully configuring the internal container runtime with docker.io credentials.

@medyagh suggested to do this before using the guest:

minikube ssh -- docker login docker.io --username ... --password ...

We will need different command for different container runtime, so maybe we need:

minikube login ...

that will do the right thing. Or maybe we can inject the docker credentials using ~/.minikube/files?

The second issue discussed in slack: https://kubernetes.slack.com/archives/C1F5CT6Q1/p1753130576600499

May 10 '25 22:05 nirs

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Aug 08 '25 22:08 k8s-triage-robot

/remove-lifecycle stale

Aug 09 '25 16:08 nirs

/kind failing-test

Aug 09 '25 16:08 nirs

/kind bug

Aug 09 '25 16:08 nirs

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Nov 08 '25 19:11 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Dec 08 '25 20:12 k8s-triage-robot

/remove-lifecycle rotten

Dec 09 '25 11:12 nirs

@medyagh can you stop the lifecycle bot trying to close this? This should be top priority and cannot be closed without fixing it.

Dec 09 '25 11:12 nirs