X Exiting due to RUNTIME_ENABLE: Failed to start container runtime: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

Akkimankar commented 5 months ago

What Happened?

stderr: E0425 15:35:39.755046 4281 remote_runtime.go:145] "Version from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" time="2024-04-25T15:35:39+05:30" level=fatal msg="getting the runtime version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\""

Attach the log file

KUBECONFIG=/root/.kube/config
Using the none driver based on existing profile
Starting "minikube" primary control-plane node in "minikube" cluster
Restarting existing none bare metal machine for "minikube" ...
OS release is Ubuntu 22.04.4 LTS

X Exiting due to RUNTIME_ENABLE: Failed to start container runtime: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: E0425 15:35:39.755046 4281 remote_runtime.go:145] "Version from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" time="2024-04-25T15:35:39+05:30" level=fatal msg="getting the runtime version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\""

Operating System

Ubuntu

Driver

VirtualBox

Sapana-Khemkar commented 4 months ago

@Akkimankar on which architecture you are facing this issue? I am facing similar issue but only on ppc64le machine not on x86.

Hhhrui commented 3 months ago

The same problem.

k8s-triage-robot commented 1 week ago

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

kubernetes / minikube