kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.47k stars 4.89k forks source link

Having issue when start minikube it is showing Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 #16066

Closed Md-Sadaf closed 9 months ago

Md-Sadaf commented 1 year ago

What Happened?

minikube start --vm-driver=none ๐Ÿ˜„ minikube v1.29.0 on Ubuntu 22.04 โœจ Using the none driver based on user configuration ๐Ÿ‘ Starting control plane node minikube in cluster minikube ๐Ÿคน Running on localhost (CPUs=4, Memory=3824MB, Disk=149597MB) ... โ„น๏ธ OS release is Ubuntu 22.04.2 LTS

โŒ Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ ๐Ÿ˜ฟ If the above advice does not help, please let us know: โ”‚ โ”‚ ๐Ÿ‘‰ https://github.com/kubernetes/minikube/issues/new/choose โ”‚ โ”‚ โ”‚ โ”‚ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

Attach the log file

minikube logs --file=logs.txt root@sadaf-Virtual:/home/sadaf# ls bin cri-dockerd Desktop Documents Downloads installer_linux logs.txt Music Pictures Public snap Templates Videos root@sadaf-Virtual:/home/sadaf# cat logs.txt

stderr: cat: /version.json: No such file or directory I0316 21:19:17.661150 4367 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" I0316 21:19:17.662240 4367 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0316 21:19:17.675103 4367 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0316 21:19:17.682205 4367 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0316 21:19:17.737240 4367 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0316 21:19:17.744436 4367 exec_runner.go:51] Run: sudo cp -a /tmp/minikube3689035833 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0316 21:19:17.775196 4367 exec_runner.go:51] Run: sudo find /etc/cni/net.d -maxdepth 1 -type f ( ( -name bridge -or -name podman ) -and -not -name .mk_disabled ) -printf "%!p(MISSING), " -exec sh -c "sudo mv {} {}.mk_disabled" ; I0316 21:19:17.799716 4367 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0316 21:19:17.799745 4367 start.go:483] detecting cgroup driver to use... I0316 21:19:17.799775 4367 detect.go:199] detected "systemd" cgroup driver on host os I0316 21:19:17.799899 4367 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///run/containerd/containerd.sock image-endpoint: unix:///run/containerd/containerd.sock " | sudo tee /etc/crictl.yaml" I0316 21:19:17.841364 4367 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )sandbox_image = .$|\1sandbox_image = "registry.k8s.io/pause:3.9"|' /etc/containerd/config.toml" W0316 21:19:17.860745 4367 start.go:450] cannot ensure containerd is configured properly and reloaded for docker - cluster might be unstable: update sandbox_image: sh -c "sudo sed -i -r 's|^( )sandbox_image = .*$|\1sandbox_image = "registry.k8s.io/pause:3.9"|' /etc/containerd/config.toml": exit status 2 stdout:

stderr: sed: can't read /etc/containerd/config.toml: No such file or directory I0316 21:19:17.860760 4367 start.go:483] detecting cgroup driver to use... I0316 21:19:17.860785 4367 detect.go:199] detected "systemd" cgroup driver on host os I0316 21:19:17.860893 4367 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///var/run/cri-dockerd.sock image-endpoint: unix:///var/run/cri-dockerd.sock " | sudo tee /etc/crictl.yaml" I0316 21:19:17.906990 4367 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0316 21:19:18.282354 4367 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0316 21:19:18.613276 4367 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0316 21:19:18.613308 4367 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0316 21:19:18.614003 4367 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1124404421 /etc/docker/daemon.json I0316 21:19:18.638381 4367 exec_runner.go:51] Run: sudo systemctl daemon-reload I0316 21:19:18.973989 4367 exec_runner.go:51] Run: sudo systemctl restart docker I0316 21:19:22.369304 4367 exec_runner.go:84] Completed: sudo systemctl restart docker: (3.395283694s) I0316 21:19:22.369352 4367 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0316 21:19:22.776209 4367 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0316 21:19:23.216644 4367 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0316 21:19:23.581894 4367 exec_runner.go:51] Run: sudo systemctl daemon-reload I0316 21:19:23.942861 4367 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0316 21:19:23.997008 4367 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0316 21:19:23.997068 4367 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0316 21:19:23.999925 4367 start.go:551] Will wait 60s for crictl version I0316 21:19:23.999983 4367 exec_runner.go:51] Run: which crictl I0316 21:19:24.010725 4367 out.go:177] W0316 21:19:24.021662 4367 out.go:239] โŒ Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

W0316 21:19:24.021701 4367 out.go:239] W0316 21:19:24.024599 4367 out.go:239] โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ ๐Ÿ˜ฟ If the above advice does not help, please let us know: โ”‚ โ”‚ ๐Ÿ‘‰ https://github.com/kubernetes/minikube/issues/new/choose โ”‚ โ”‚ โ”‚ โ”‚ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ I0316 21:19:24.035541 4367 out.go:177]

Operating System

Ubuntu

Driver

None

k8s-triage-robot commented 1 year 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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

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-triage-robot commented 9 months ago

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-ci-robot commented 9 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/16066#issuecomment-1901271576): >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: >- 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.