kubernetes / minikube

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

minikube start issue #15896

Closed vamsibyramala closed 1 year ago

vamsibyramala commented 1 year ago

What Happened?

minikube start --vm-driver=none

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

stderr: E0221 05:24:48.519744 5701 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-02-21T05:24:48Z" 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: cat: /version.json: No such file or directory I0221 05:24:11.387738 5275 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" W0221 05:24:11.389417 5275 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0221 05:24:11.389487 5275 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0221 05:24:11.400226 5275 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0221 05:24:11.400239 5275 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0221 05:24:11.400278 5275 exec_runner.go:51] Run: sudo rm -f /etc/systemd/system/cri-docker.service.d/10-cni.conf I0221 05:24:11.411362 5275 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0221 05:24:11.411487 5275 exec_runner.go:51] Run: sudo cp -a /tmp/minikube3329676874 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0221 05:24:11.425001 5275 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" ; I0221 05:24:11.436339 5275 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0221 05:24:11.436356 5275 start.go:483] detecting cgroup driver to use... I0221 05:24:11.436381 5275 detect.go:199] detected "systemd" cgroup driver on host os I0221 05:24:11.436499 5275 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" I0221 05:24:11.463549 5275 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" W0221 05:24:11.478540 5275 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 I0221 05:24:11.478572 5275 start.go:483] detecting cgroup driver to use... I0221 05:24:11.478596 5275 detect.go:199] detected "systemd" cgroup driver on host os I0221 05:24:11.478703 5275 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" I0221 05:24:11.504906 5275 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0221 05:24:11.769406 5275 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0221 05:24:12.031854 5275 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0221 05:24:12.031883 5275 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0221 05:24:12.031889 5275 exec_runner.go:207] rm: /etc/docker/daemon.json I0221 05:24:12.031926 5275 exec_runner.go:51] Run: sudo rm -f /etc/docker/daemon.json I0221 05:24:12.044720 5275 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0221 05:24:12.044879 5275 exec_runner.go:51] Run: sudo cp -a /tmp/minikube118025388 /etc/docker/daemon.json I0221 05:24:12.060804 5275 exec_runner.go:51] Run: sudo systemctl daemon-reload I0221 05:24:12.320315 5275 exec_runner.go:51] Run: sudo systemctl restart docker I0221 05:24:12.649187 5275 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0221 05:24:12.912302 5275 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0221 05:24:13.165048 5275 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0221 05:24:13.444181 5275 exec_runner.go:51] Run: sudo systemctl daemon-reload I0221 05:24:13.688779 5275 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0221 05:24:13.723400 5275 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0221 05:24:13.723480 5275 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0221 05:24:13.724975 5275 start.go:551] Will wait 60s for crictl version I0221 05:24:13.725006 5275 exec_runner.go:51] Run: which crictl I0221 05:24:13.725968 5275 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0221 05:24:15.794305 5275 exec_runner.go:84] Completed: sudo /usr/local/bin/crictl version: (2.068303758s) I0221 05:24:15.794334 5275 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: E0221 05:24:15.791687 5680 remote_runtime.go:145] "Version from runtime service failed" err="rpc error: code = Unavailable desc = connection closed before server preface received" time="2023-02-21T05:24:15Z" level=fatal msg="getting the runtime version: rpc error: code = Unavailable desc = connection closed before server preface received" I0221 05:24:26.842133 5275 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0221 05:24:26.878089 5275 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: E0221 05:24:26.875348 5694 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-02-21T05:24:26Z" 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\"" I0221 05:24:48.485967 5275 exec_runner.go:51] Run: sudo /usr/local/bin/crictl version I0221 05:24:48.525222 5275 out.go:177] W0221 05:24:48.527460 5275 out.go:239] X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 stdout:

stderr: E0221 05:24:48.519744 5701 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-02-21T05:24:48Z" 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\""

W0221 05:24:48.527494 5275 out.go:239] W0221 05:24:48.528603 5275 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0221 05:24:48.530438 5275 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 1 year 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 1 year ago

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

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