Minikube start failure #14456
Labels
co/kvm2-driver
KVM2 driver related issues
kind/support
Categorizes issue or PR as a support question.
long-term-support
Long-term support issues that can't be fixed in code
Comments
|
|
@spowelljr if using --driver=kvm2 is cri-dockerd still needed for minikube 1.26.0? |
Even if it is, shouldn't I have seen the error during the initial start ? |
|
Hi @kashifest, thanks for reporting your issue with minikube. If you don't provide a If I have time today I'll try replicating this and see if I run into the same issue. |
spowelljr
added
kind/support
|
So I tried this on my own machine and didn't experience what you are getting, mine restarted correctly as I would expect. This is an odd error as it seems like Also, I see you're running |
@spowelljr thanks for testing it. I guess sudo is not the issue here. I noticed that its just taking more time to get the crictl starting than the initial 3 times try. I got a workaround by adding a loop like this: I will give a small gist of the times it tried: So basically instead of trying 3 times only it needed to try 9 times. I believe trying 3 times only and/or the |
|
Thanks for figuring this out @kashifest! I will say that 60 seconds seems like a long time for the container runtime to come up, but this is the first case of this I've seen reported yet, so maybe like you said it's isolated to certain environments. |
spowelljr
added
the
long-term-support
|
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 |
k8s-ci-robot
added
the
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 |
k8s-ci-robot
added
lifecycle/rotten
|
@spowelljr I am still seeing this issue and probably with more delay needed with newer versions, is it possible to configure the timeout? |
kashifest
added a commit
to Nordix/metal3-dev-env
that referenced
this issue
Dec 22, 2022
… cri to comeup which exceeds default hardcoded timeout 60 seconds. Hence we need to try in loop. Upstream issue is kubernetes/minikube#14456
furkatgofurov7
pushed a commit
to Nordix/metal3-dev-env
that referenced
this issue
Dec 23, 2022
… cri to comeup which exceeds default hardcoded timeout 60 seconds. Hence we need to try in loop. Upstream issue is kubernetes/minikube#14456
kashifest
added a commit
to Nordix/metal3-dev-env
that referenced
this issue
Jan 2, 2023
… cri to comeup which exceeds default hardcoded timeout 60 seconds. Hence we need to try in loop. Upstream issue is kubernetes/minikube#14456
|
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. |
|
/reopen |
|
@kashifest: Reopened this issue. 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-sigs/prow repository. |
k8s-ci-robot
removed
the
lifecycle/rotten
kashifest
added a commit
to Nordix/baremetal-operator
that referenced
this issue
Oct 4, 2024
This is a workaround for a long existing issue in minikube which we opened long ago but it seems it has not gone away. Here is the issue for more detail kubernetes/minikube#14456 Signed-off-by: Kashif Khan <kashif.khan@est.tech>
kashifest
added a commit
to Nordix/baremetal-operator
that referenced
this issue
Oct 4, 2024
This is a workaround for a long existing issue in minikube which we opened long ago but it seems it has not gone away. Here is the issue for more detail kubernetes/minikube#14456 Signed-off-by: Kashif Khan <kashif.khan@est.tech>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Happened?
minikube restart failing . We first create a minikube with --driver=kvm2. First start is successful. We then need to stop minikube and do some more configuration and later we restart the minikube again. The second start is failing. Attaching the first and the second minikube start here.
Attach the log file
First
Second
Operating System
No response
Driver
No response
The text was updated successfully, but these errors were encountered: