search

kubernetes / minikube

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

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\"" #16198

Closed Rajan251 closed 7 months ago

Rajan251 commented 1 year ago

What Happened?

stderr: E0330 17:57:03.593552 6708 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="2023-03-30T17:57:03+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

stderr: I0330 17:56:24.491892 6079 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0330 17:56:24.503507 6079 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0330 17:56:24.503520 6079 fix.go:129] unexpected machine state, will restart: I0330 17:56:24.504816 6079 out.go:177] 🔄 Restarting existing none bare metal machine for "minikube" ... I0330 17:56:24.506623 6079 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0330 17:56:24.506761 6079 start.go:300] post-start starting for "minikube" (driver="none") I0330 17:56:24.506810 6079 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] I0330 17:56:24.506837 6079 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 I0330 17:56:24.514339 6079 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0330 17:56:24.515616 6079 out.go:177] ℹ️ OS release is Kali GNU/Linux Rolling I0330 17:56:24.516457 6079 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0330 17:56:24.516718 6079 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0330 17:56:24.516920 6079 start.go:303] post-start completed in 10.151847ms I0330 17:56:24.516926 6079 fix.go:57] fixHost completed within 50.243248ms I0330 17:56:24.516930 6079 start.go:83] releasing machines lock for "minikube", held for 50.255161ms I0330 17:56:24.517227 6079 exec_runner.go:51] Run: cat /version.json I0330 17:56:24.517935 6079 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0330 17:56:24.518093 6079 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0330 17:56:24.518135 6079 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" W0330 17:56:24.520730 6079 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0330 17:56:24.520800 6079 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0330 17:56:24.528653 6079 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0330 17:56:24.528663 6079 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0330 17:56:24.528724 6079 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0330 17:56:24.528838 6079 exec_runner.go:51] Run: sudo cp -a /tmp/minikube3988080919 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0330 17:56:24.535637 6079 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" ; I0330 17:56:24.543740 6079 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0330 17:56:24.543757 6079 start.go:483] detecting cgroup driver to use... I0330 17:56:24.543776 6079 detect.go:199] detected "systemd" cgroup driver on host os I0330 17:56:24.543879 6079 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" I0330 17:56:24.566017 6079 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" I0330 17:56:24.573266 6079 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" I0330 17:56:24.581249 6079 containerd.go:145] configuring containerd to use "systemd" as cgroup driver... I0330 17:56:24.581289 6079 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )SystemdCgroup = .$|\1SystemdCgroup = true|g' /etc/containerd/config.toml" I0330 17:56:24.588982 6079 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" I0330 17:56:24.596551 6079 exec_runner.go:51] Run: sh -c "sudo sed -i '/systemd_cgroup/d' /etc/containerd/config.toml" I0330 17:56:24.603835 6079 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runc.v1"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0330 17:56:24.611165 6079 exec_runner.go:51] Run: sh -c "sudo rm -rf /etc/cni/net.mk" I0330 17:56:24.618306 6079 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" I0330 17:56:24.626410 6079 exec_runner.go:51] Run: sudo sysctl net.bridge.bridge-nf-call-iptables I0330 17:56:24.633032 6079 exec_runner.go:51] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" I0330 17:56:24.639057 6079 exec_runner.go:51] Run: sudo systemctl daemon-reload I0330 17:56:24.999480 6079 exec_runner.go:51] Run: sudo systemctl restart containerd I0330 17:56:25.105255 6079 start.go:483] detecting cgroup driver to use... I0330 17:56:25.105285 6079 detect.go:199] detected "systemd" cgroup driver on host os I0330 17:56:25.105387 6079 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" I0330 17:56:25.131685 6079 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0330 17:56:25.499241 6079 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0330 17:56:25.843041 6079 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0330 17:56:25.843066 6079 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0330 17:56:25.843072 6079 exec_runner.go:207] rm: /etc/docker/daemon.json I0330 17:56:25.843145 6079 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0330 17:56:25.843275 6079 exec_runner.go:51] Run: sudo cp -a /tmp/minikube2202084233 /etc/docker/daemon.json I0330 17:56:25.849828 6079 exec_runner.go:51] Run: sudo systemctl daemon-reload I0330 17:56:26.227969 6079 exec_runner.go:51] Run: sudo systemctl restart docker I0330 17:56:27.069718 6079 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0330 17:56:27.443238 6079 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0330 17:56:27.810836 6079 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0330 17:56:28.167637 6079 exec_runner.go:51] Run: sudo systemctl daemon-reload I0330 17:56:28.523450 6079 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0330 17:56:28.555211 6079 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0330 17:56:28.555274 6079 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0330 17:56:28.557392 6079 start.go:551] Will wait 60s for crictl version I0330 17:56:28.557419 6079 exec_runner.go:51] Run: which crictl I0330 17:56:28.558308 6079 exec_runner.go:51] Run: sudo /usr/bin/crictl version I0330 17:56:30.866306 6079 exec_runner.go:84] Completed: sudo /usr/bin/crictl version: (2.307963697s) I0330 17:56:30.866345 6079 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo /usr/bin/crictl version: exit status 1 stdout:

stderr: E0330 17:56:30.862770 6624 remote_runtime.go:145] "Version from runtime service failed" err="rpc error: code = Unavailable desc = connection closed before server preface received" time="2023-03-30T17:56:30+05:30" level=fatal msg="getting the runtime version: rpc error: code = Unavailable desc = connection closed before server preface received" I0330 17:56:41.913331 6079 exec_runner.go:51] Run: sudo /usr/bin/crictl version I0330 17:56:41.950129 6079 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo /usr/bin/crictl version: exit status 1 stdout:

stderr: E0330 17:56:41.946688 6646 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="2023-03-30T17:56:41+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\"" I0330 17:57:03.560190 6079 exec_runner.go:51] Run: sudo /usr/bin/crictl version I0330 17:57:03.598088 6079 out.go:177] W0330 17:57:03.600067 6079 out.go:239] ❌ Exiting due to RUNTIME_ENABLE: Temporary Error: sudo /usr/bin/crictl version: exit status 1 stdout:

stderr: E0330 17:57:03.593552 6708 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="2023-03-30T17:57:03+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\""

W0330 17:57:03.600105 6079 out.go:239] W0330 17:57:03.602090 6079 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. │ │ │ ╰───────────────────────────────────────────────────────────────────────────────────────────╯ I0330 17:57:03.603085 6079 out.go:177]

Operating System

Other

Driver

None (Baremetal)

kundan2707 commented 1 year ago

/kind support

afbjorklund commented 1 year ago

There should be some more information available in minikube ssh sudo systemctl status cri-dockerd

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

kundan2707 commented 1 year ago

/remove-lifecycle stale

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

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

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