why minikube start pull image with hash even when using image-mirror, which leads always fail

[darkSheep404]

What Happened?

i using this command to use image-mirror
minikube start --driver=docker --image-mirror-country='cn' --image-repository='registry.cn-hangzhou.aliyuncs.com/google_containers'

But
there is a image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45
but no image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85

so will always fail ..

may i know how can i let it ignore image hash, just pull kicbase:v0.0.45 from registry.cn-hangzhou.aliyuncs.com

It would be really helpful if anyone could help --- from a desperate Chinese developer

output

😄  minikube v1.34.0 on Ubuntu 22.04 (amd64)
✨  Using the docker driver based on user configuration
✅  Using image repository registry.cn-hangzhou.aliyuncs.com/google_containers
📌  Using Docker driver with root privileges
👍  Starting "minikube" primary control-plane node in "minikube" cluster
🚜  Pulling base image v0.0.45 ...
E1213 11:09:57.618696   15638 cache.go:189] Error downloading kic artifacts:  failed to download kic base image or any fallback image
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
🤦  StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85 -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85' locally
docker: Error response from daemon: manifest for registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85 not found: manifest unknown: manifest unknown.
See 'docker run --help'.

Attach the log file

$ minikube logs --file=log.txt

❌ Exiting due to GUEST_STATUS: Unable to get control-plane node minikube host status: state: unknown state "minikube": docker container inspect minikube --format={{.State.Status}}: exit status 1
stdout:

stderr:
Error response from daemon: No such container: minikube

Operating System

Windows

Driver

Docker

[darkSheep404]

finally fixed by minikube start --vm-driver=docker --kubernetes-version='1.28' --base-image=registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45
using --base-image=registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.45 and works