search

kubernetes / minikube

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

Minikube start command is not working #17155

Closed sureshops111 closed 1 year ago

sureshops111 commented 1 year ago

What Happened?

root@ip-172-31-7-230:~# minikube start --vm-driver=none 😄 minikube v1.31.2 on Ubuntu 22.04 (xen/amd64) ✨ Using the none driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🔄 Restarting existing none bare metal machine for "minikube" ... ℹ️ OS release is Ubuntu 22.04.2 LTS

❌ Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker: exit status 1 stdout:

stderr: Job for cri-docker.service failed because the control process exited with error code. See "systemctl status cri-docker.service" and "journalctl -xeu cri-docker.service" for details.

Attach the log file

*

stderr: I0830 04:27:15.794880 12644 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0830 04:27:15.808038 12644 fix.go:102] recreateIfNeeded on minikube: state=Stopped err= W0830 04:27:15.808054 12644 fix.go:128] unexpected machine state, will restart: I0830 04:27:15.815514 12644 out.go:177] 🔄 Restarting existing none bare metal machine for "minikube" ... I0830 04:27:15.819353 12644 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0830 04:27:15.819514 12644 start.go:300] post-start starting for "minikube" (driver="none") I0830 04:27:15.819553 12644 start.go:329] creating required directories: [/etc/kubernetes/addons /etc/kubernetes/manifests /var/tmp/minikube /var/lib/minikube /var/lib/minikube/certs /var/lib/minikube/images /var/lib/minikube/binaries /tmp/gvisor /usr/share/ca-certificates /etc/ssl/certs] I0830 04:27:15.819593 12644 exec_runner.go:51] Run: sudo mkdir -p /etc/kubernetes/addons /etc/kubernetes/manifests /var/tmp/minikube /var/lib/minikube /var/lib/minikube/certs /var/lib/minikube/images /var/lib/minikube/binaries /tmp/gvisor /usr/share/ca-certificates /etc/ssl/certs I0830 04:27:15.829951 12644 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0830 04:27:15.829979 12644 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0830 04:27:15.829990 12644 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0830 04:27:15.836593 12644 out.go:177] ℹ️ OS release is Ubuntu 22.04.2 LTS I0830 04:27:15.839345 12644 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0830 04:27:15.839407 12644 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0830 04:27:15.839433 12644 start.go:303] post-start completed in 19.9095ms I0830 04:27:15.839441 12644 fix.go:56] fixHost completed within 61.72362ms I0830 04:27:15.839447 12644 start.go:83] releasing machines lock for "minikube", held for 61.781974ms I0830 04:27:15.839808 12644 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" I0830 04:27:15.840083 12644 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ I0830 04:27:15.849219 12644 exec_runner.go:51] Run: sudo find /etc/cni/net.d -maxdepth 1 -type f -name loopback.conf -not -name .mk_disabled -exec sh -c "grep -q loopback {} && ( grep -q name {} || sudo sed -i '/"type": "loopback"/i \ \ \ \ "name": "loopback",' {} ) && sudo sed -i 's|"cniVersion": "."|"cniVersion": "1.0.0"|g' {}" ; I0830 04:27:15.874703 12644 cni.go:230] loopback cni configuration patched: "/etc/cni/net.d/loopback.conf" found I0830 04:27:15.874784 12644 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" ; I0830 04:27:15.885275 12644 cni.go:259] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0830 04:27:15.885290 12644 start.go:466] detecting cgroup driver to use... I0830 04:27:15.885332 12644 detect.go:199] detected "systemd" cgroup driver on host os I0830 04:27:15.885447 12644 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///run/containerd/containerd.sock " | sudo tee /etc/crictl.yaml" I0830 04:27:15.906835 12644 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" W0830 04:27:15.919103 12644 start.go:433] 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 I0830 04:27:15.919118 12644 start.go:466] detecting cgroup driver to use... I0830 04:27:15.919150 12644 detect.go:199] detected "systemd" cgroup driver on host os I0830 04:27:15.919252 12644 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///var/run/cri-dockerd.sock " | sudo tee /etc/crictl.yaml" I0830 04:27:15.941925 12644 exec_runner.go:51] Run: which cri-dockerd I0830 04:27:15.942980 12644 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0830 04:27:15.953911 12644 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0830 04:27:15.953925 12644 exec_runner.go:203] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0830 04:27:15.953981 12644 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (195 bytes) I0830 04:27:15.954112 12644 exec_runner.go:51] Run: sudo cp -a /tmp/minikube3254840142 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0830 04:27:15.964217 12644 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0830 04:27:16.202696 12644 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0830 04:27:16.460837 12644 docker.go:535] configuring docker to use "systemd" as cgroup driver... I0830 04:27:16.460863 12644 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0830 04:27:16.460870 12644 exec_runner.go:203] rm: /etc/docker/daemon.json I0830 04:27:16.460931 12644 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0830 04:27:16.461081 12644 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1208422488 /etc/docker/daemon.json I0830 04:27:16.472257 12644 exec_runner.go:51] Run: sudo systemctl daemon-reload I0830 04:27:16.723315 12644 exec_runner.go:51] Run: sudo systemctl restart docker I0830 04:27:17.180936 12644 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0830 04:27:17.434919 12644 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0830 04:27:17.683143 12644 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0830 04:27:17.947208 12644 exec_runner.go:51] Run: sudo systemctl daemon-reload I0830 04:27:18.211188 12644 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0830 04:27:18.241333 12644 exec_runner.go:51] Run: sudo systemctl daemon-reload I0830 04:27:18.479351 12644 exec_runner.go:51] Run: sudo systemctl restart cri-docker I0830 04:27:18.582465 12644 out.go:177] W0830 04:27:18.588696 12644 out.go:239] ❌ Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker: exit status 1 stdout:

stderr: Job for cri-docker.service failed because the control process exited with error code. See "systemctl status cri-docker.service" and "journalctl -xeu cri-docker.service" for details.

W0830 04:27:18.588979 12644 out.go:239] W0830 04:27:18.590069 12644 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. │ │ │ ╰───────────────────────────────────────────────────────────────────────────────────────────╯ I0830 04:27:18.592403 12644 out.go:177]

Operating System

None

Driver

None

afbjorklund commented 1 year ago

See "systemctl status cri-docker.service" and "journalctl -xeu cri-docker.service" for details.

Looks like a problem with cri-dockerd, verify with crictl version or something like that...

thrishul1989 commented 1 year ago

try to restart thr machine and enable the container runtime using this commmand sudo systemctl restart cri-docker

spowelljr commented 1 year ago

Hi @sureshops111, we haven't heard back from you, do you still have this issue? There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.