Exiting due to K8S_INSTALL_FAILED

[JeffSG]

What Happened?

Run below command
minikube start --driver=docker --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --alsologtostderr
Got below error
Exiting due to K8S_INSTALL_FAILED: updating control plane: downloading binaries: downloading kubeadm: download failed: https://kubernetes.oss-cn-hangzhou.aliyuncs.com/kubernetes-release/release/v1.20.2/bin/linux/amd64/kubeadm?checksum=file:https://kubernetes.oss-cn-hangzhou.aliyuncs.com/kubernetes-release/release/v1.20.2/bin/linux/amd64/kubeadm.sha256: getter: &{Ctx:context.Background Src:https://kubernetes.oss-cn-hangzhou.aliyuncs.com/kubernetes-release/release/v1.20.2/bin/linux/amd64/kubeadm?checksum=file:https://kubernetes.oss-cn-hangzhou.aliyuncs.com/kubernetes-release/release/v1.20.2/bin/linux/amd64/kubeadm.sha256 Dst:C:\Users\Administrator\.minikube\cache\linux\v1.20.2/kubeadm.download Pwd: Mode:2 Umask:---------- Detectors:[0x3b2c050 0x3b2c050 0x3b2c050 0x3b2c050 0x3b2c050 0x3b2c050 0x3b2c050] Decompressors:map[bz2:0x3b2c050 gz:0x3b2c050 tar.bz2:0x3b2c050 tar.gz:0x3b2c050 tar.xz:0x3b2c050 tar.zst:0x3b2c050 tbz2:0x3b2c050 tgz:0x3b2c050 txz:0x3b2c050 tzst:0x3b2c050 xz:0x3b2c050 zip:0x3b2c050 zst:0x3b2c050] Getters:map[file:0xc0007d83e0 http:0xc0004d3ae0 https:0xc0004d3b00] Dir:false ProgressListener:0x3ad7ea0 Options:[0x22f7a60]}: invalid checksum: Error downloading checksum file: bad response code: 404

Attach the log file

lastStart.txt

Operating System

Windows

Driver

Docker

[liangyuanpeng]

I think it need to create a issue to https://github.com/kubernetes/minikube/issues

[JeffSG]

I think it need to create a issue to https://github.com/kubernetes/minikube/issues

Isn't it here?

[liangyuanpeng]

@JeffSG Ohh, i put the wrong thing, i mean here https://github.com/AliyunContainerService/minikube/issues, the reason is you're download file from aliyuncs with param of --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers

[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

[pigga]

看了这么久，好像没发现有解决方案了。阿里的仓库应该是太久了。好久没更新了，最新的 版本为1.23。所以最终的解决方案是啥？ so , what's the really result？