'minikube start --container-runtime=cri-o --wait=all' fails: time out waiting for condition - v1.24.0 #12928
Comments
|
I found an issue on the cri-o github from Aug 2020 that looks amazingly similar: cri-o/cri-o#3555. They closed it with a "disable ipv6" workaround. |
|
We ran into this today when upgrading Some more version information: It did actually launch correctly on another machine I have which has an older kernel: So it may be kernel version related. |
|
Hi @johnmuth81, were you able to disable A new release is on its way, which may help to further resolve this issue. |
|
Hi @johnmuth81, we haven't heard back from you, do you still have this issue? I will close this issue for now but feel free to reopen when you feel ready to provide more information. |
|
Hi @spowelljr ! This is still an issue for us with minikube 1.25.1. We are using Ubuntu 20.04. To reproduce I:
I then ran the command in the original issue: And got the same effect, Additional version information: Is there any more information that would be useful? |
|
Hi @jszwedko, your kube-proxy error seems to be This seems related to LXC itself, here's a related issue: https://serverfault.com/q/946854 |
|
Ah, I see. Thanks for the response and the link! I'm still not completely following though, how would I apply the recommendations there to minikube? My same system is able to run |
|
Hi all, I deep dived into the issue and found out the root cause is a missing capabilities in the minikube Or you can check the capabilities in the container by: we can see Currently, I see running a test docker release as an only workaround. I will add comment to the fix that it should be back ported to stable release. |
|
@spowelljr any thoughts on this? |
|
I'm experiencing the same error right now by running:
The pod/kube-proxy-vxrrm still with status CreateContainerError
|
Sorry for the delay, thanks for the deep dive on the issue, it makes complete sense why it's not working. We should warn users about this when they try to start minikube with docker and cri-o and link them to this issue. Unfortunately it doesn't seem like there's anything else we can do from our side. Once Docker makes the version with the fix GA we can update the message to suggest users to update to the latest Docker version. |
spowelljr
added
co/runtime/crio
|
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. This bot triages un-triaged issues 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
|
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. |
There was an issue running minikube with --container-runtime=cri-o in GitHub actions due toversion older than v0.23.0 kubernetes/minikube#12928 (comment).
There was an issue running minikube with --container-runtime=cri-o in GitHub actions due to docker version older than v0.23.0 kubernetes/minikube#12928 (comment). Signed-off-by: Qasim Sarfraz <qasimsarfraz@microsoft.com>
There was an issue running minikube with --container-runtime=cri-o in GitHub actions due to docker version older than v0.23.0 kubernetes/minikube#12928 (comment). Signed-off-by: Qasim Sarfraz <qasimsarfraz@microsoft.com>
Minikube Version: v1.24.0
System: Linux. Ubuntu 20.04, Fedora 33
Running
kubectl get pod -Afrom another terminal:Output from
minikube logs:The text was updated successfully, but these errors were encountered: