-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
start failure in qemu, need k8s.gcr.io/pause:3.6 not 3.7 #14641
Comments
Currently there is no way to specify the sandbox image in cri-dockerd, so it will need to have both. Before 1.24, it was possible to select which version to use using Now it is decoupled (from the kubelet), so it needs to be updated manually in the CRI configuration.
The same setting needs to be reflected, also for the containerd and for the cri-o configuration.
Missing from https://github.com/kubernetes/minikube/blob/master/pkg/minikube/cruntime/docker.go |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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/test-infra repository. |
What Happened?
It's too long.
Log file:
minikube-start.log
Attach the log file
Oh~~~, i can not log detail...
So, i export some log about kubelet service with
journalctl -u kubelet > logs.txt
, file is here:log.txt
Key of the problem is :
"RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed pulling image \"k8s.gcr.io/pause:3.6\": Error response from daemon: Get \"https://k8s.gcr.io/v2/\": dial tcp: lookup k8s.gcr.io on 10.0.2.3:53: read udp 10.0.2.15:47398->10.0.2.3:53: i/o timeout"
Look at images in docker:
k8s.gcr.io/pause:3.7
in vm, but we need3.6
when start minikube.=============
Let's pass proxy env to docker env, then we can pull the image we need by proxy.
Nice !!! minikube started.
Look at images in docker:
k8s.gcr.io/pause:3.6
in vm now, and3.7
is also in.And
k8s.gcr.io/pause:3.6
is used.So, can we fix it???
Operating System
macos m1
Driver
qemu
The text was updated successfully, but these errors were encountered: