E0812 20:12:27.352446 17560 cache.go:189] Error downloading kic artifacts: failed to download kic base image or any fallback image

[linhaishan]

What Happened?

In China, starting minikube based on window failed， Error downloading kic artifacts: failed to download kic base image or any fallback image.
minikube start --base-image "gcr.io/k8s-minikube/kicbase:v0.0.32"

Attach the log file

Uploading lastStart.txt…

Operating System

Windows

Driver

Docker

[liangyuanpeng]

/kind support

yes, china can not access gcr.io, it's a network issue. try to add a flag --image-mirror-country=cn

[linhaishan]

Hi Lan，I still have this problem after using the following command. How can I solve it. Environment: Using Docker Desktop (Docker) , minikube, Hyper-V, and WSI on Windows minikube stop minikube delete  minikube start  There is still a failed to download kic base image or any fallback image issue. || 

…

------------------ 原始邮件 ------------------ 发件人: "kubernetes/minikube" ***@***.***>; 发送时间: 2024年8月13日(星期二) 下午5:31 ***@***.***>; ***@***.******@***.***>; 主题: Re: [kubernetes/minikube] E0812 20:12:27.352446 17560 cache.go:189] Error downloading kic artifacts: failed to download kic base image or any fallback image (Issue #19413) /kind support yes, china can not access gcr.io, it's a network issue. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[k8s-triage-robot]

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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[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:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.