search

kubernetes / minikube

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

Minikube not start #16027

Closed rragul closed 8 months ago

rragul commented 1 year ago

What Happened?

minikube start

😄 minikube v1.29.0 on Ubuntu 22.04 ✨ 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: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: time="2023-03-11T12:30:39+05:30" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\""

╭───────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ 😿 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

stderr: I0311 12:32:37.196444 46881 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0311 12:32:37.204206 46881 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0311 12:32:37.204218 46881 fix.go:129] unexpected machine state, will restart: I0311 12:32:37.204982 46881 out.go:177] 🔄 Restarting existing none bare metal machine for "minikube" ... I0311 12:32:37.206558 46881 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0311 12:32:37.206646 46881 start.go:300] post-start starting for "minikube" (driver="none") I0311 12:32:37.206665 46881 start.go:328] 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] I0311 12:32:37.206682 46881 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 I0311 12:32:37.212296 46881 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0311 12:32:37.212313 46881 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0311 12:32:37.212319 46881 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0311 12:32:37.212980 46881 out.go:177] ℹ️ OS release is Ubuntu 22.04.2 LTS I0311 12:32:37.213487 46881 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0311 12:32:37.213510 46881 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0311 12:32:37.213521 46881 start.go:303] post-start completed in 6.870747ms I0311 12:32:37.213525 46881 fix.go:57] fixHost completed within 31.785582ms I0311 12:32:37.213528 46881 start.go:83] releasing machines lock for "minikube", held for 31.792908ms I0311 12:32:37.213817 46881 exec_runner.go:51] Run: cat /version.json I0311 12:32:37.213926 46881 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0311 12:32:37.214314 46881 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0311 12:32:37.214344 46881 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" W0311 12:32:37.215429 46881 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0311 12:32:37.215478 46881 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0311 12:32:37.221329 46881 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0311 12:32:37.221336 46881 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0311 12:32:37.221373 46881 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0311 12:32:37.221466 46881 exec_runner.go:51] Run: sudo cp -a /tmp/minikube11277273 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0311 12:32:37.227302 46881 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" ; I0311 12:32:37.232923 46881 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0311 12:32:37.232931 46881 start.go:483] detecting cgroup driver to use... I0311 12:32:37.232946 46881 detect.go:199] detected "systemd" cgroup driver on host os I0311 12:32:37.233027 46881 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" I0311 12:32:37.244894 46881 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" I0311 12:32:37.250917 46881 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )restrict_oom_score_adj = .$|\1restrict_oom_score_adj = false|' /etc/containerd/config.toml" I0311 12:32:37.257121 46881 containerd.go:145] configuring containerd to use "systemd" as cgroup driver... I0311 12:32:37.257144 46881 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )SystemdCgroup = .$|\1SystemdCgroup = true|g' /etc/containerd/config.toml" I0311 12:32:37.263061 46881 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runtime.v1.linux"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0311 12:32:37.269286 46881 exec_runner.go:51] Run: sh -c "sudo sed -i '/systemd_cgroup/d' /etc/containerd/config.toml" I0311 12:32:37.275724 46881 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runc.v1"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0311 12:32:37.282064 46881 exec_runner.go:51] Run: sh -c "sudo rm -rf /etc/cni/net.mk" I0311 12:32:37.287920 46881 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )conf_dir = .*$|\1conf_dir = "/etc/cni/net.d"|g' /etc/containerd/config.toml" I0311 12:32:37.293910 46881 exec_runner.go:51] Run: sudo sysctl net.bridge.bridge-nf-call-iptables I0311 12:32:37.299228 46881 exec_runner.go:51] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" I0311 12:32:37.304589 46881 exec_runner.go:51] Run: sudo systemctl daemon-reload I0311 12:32:37.643147 46881 exec_runner.go:51] Run: sudo systemctl restart containerd I0311 12:32:37.694760 46881 start.go:483] detecting cgroup driver to use... I0311 12:32:37.694786 46881 detect.go:199] detected "systemd" cgroup driver on host os I0311 12:32:37.694902 46881 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" I0311 12:32:37.707415 46881 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0311 12:32:38.072386 46881 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0311 12:32:38.436097 46881 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0311 12:32:38.436116 46881 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0311 12:32:38.436121 46881 exec_runner.go:207] rm: /etc/docker/daemon.json I0311 12:32:38.436167 46881 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0311 12:32:38.436258 46881 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1692790957 /etc/docker/daemon.json I0311 12:32:38.442258 46881 exec_runner.go:51] Run: sudo systemctl daemon-reload I0311 12:32:38.788471 46881 exec_runner.go:51] Run: sudo systemctl restart docker I0311 12:32:39.638210 46881 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0311 12:32:39.958011 46881 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0311 12:32:40.324298 46881 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0311 12:32:40.678948 46881 exec_runner.go:51] Run: sudo systemctl daemon-reload I0311 12:32:41.020532 46881 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0311 12:32:41.030470 46881 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0311 12:32:41.030495 46881 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0311 12:32:41.031269 46881 start.go:551] Will wait 60s for crictl version I0311 12:32:41.031288 46881 exec_runner.go:51] Run: which crictl I0311 12:32:41.031775 46881 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0311 12:32:43.055317 46881 exec_runner.go:84] Completed: sudo /usr/local/bin/crictl version: (2.02349702s) I0311 12:32:43.055401 46881 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: time="2023-03-11T12:32:43+05:30" level=fatal msg="unable to determine runtime API version: rpc error: code = DeadlineExceeded desc = context deadline exceeded" I0311 12:32:54.103883 46881 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0311 12:32:54.128824 46881 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: time="2023-03-11T12:32:54+05:30" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" I0311 12:33:15.737570 46881 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0311 12:33:15.765347 46881 out.go:177] W0311 12:33:15.766045 46881 out.go:239] ❌ Exiting due to RUNTIME_ENABLE: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: time="2023-03-11T12:33:15+05:30" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\""

W0311 12:33:15.766059 46881 out.go:239] W0311 12:33:15.766872 46881 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. │ │ │ ╰───────────────────────────────────────────────────────────────────────────────────────────╯ I0311 12:33:15.767655 46881 out.go:177]

Operating System

Ubuntu

Driver

KVM2

afbjorklund commented 1 year ago

Check that docker (including cri-dockerd) has been installed correctly, and that crictl version works OK ?

Sometimes this is caused by not using the packages, but something like cp -a to install the systemd units

rragul commented 1 year ago

Check that docker (including cri-dockerd) has been installed correctly, and that crictl version works OK ?

Sometimes this is caused by not using the packages, but something like cp -a to install the systemd units

crictl version FATA[0000] unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused"

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 8 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 8 months ago

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

In response to [this](https://github.com/kubernetes/minikube/issues/16027#issuecomment-1900581022): >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.