search

kubernetes / minikube

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

Not able start minikube #14792

Closed umeshsoni2 closed 1 year ago

umeshsoni2 commented 2 years ago

What Happened?

Not start minikube.

Attach the log file

stderr: I0815 04:49:29.894292 8106 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0815 04:49:29.904285 8106 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0815 04:49:29.904300 8106 fix.go:129] unexpected machine state, will restart: I0815 04:49:29.906756 8106 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0815 04:49:29.909696 8106 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0815 04:49:29.909837 8106 start.go:307] post-start starting for "minikube" (driver="none") I0815 04:49:29.909883 8106 start.go:335] 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] I0815 04:49:29.909921 8106 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 I0815 04:49:29.920484 8106 main.go:134] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0815 04:49:29.920505 8106 main.go:134] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0815 04:49:29.920517 8106 main.go:134] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0815 04:49:29.923821 8106 out.go:177] OS release is Ubuntu 18.04.6 LTS I0815 04:49:29.925846 8106 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0815 04:49:29.925907 8106 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0815 04:49:29.925951 8106 start.go:310] post-start completed in 16.10309ms I0815 04:49:29.925960 8106 fix.go:57] fixHost completed within 45.890376ms I0815 04:49:29.925967 8106 start.go:82] releasing machines lock for "minikube", held for 45.911449ms I0815 04:49:29.926403 8106 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" I0815 04:49:29.926522 8106 exec_runner.go:51] Run: curl -sS -m 2 https://k8s.gcr.io/ I0815 04:49:29.955588 8106 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0815 04:49:30.109421 8106 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0815 04:49:30.238634 8106 exec_runner.go:51] Run: sudo systemctl daemon-reload I0815 04:49:30.390713 8106 exec_runner.go:51] Run: sudo systemctl restart docker I0815 04:49:30.695727 8106 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0815 04:49:30.866028 8106 exec_runner.go:51] Run: sudo systemctl daemon-reload I0815 04:49:31.034723 8106 exec_runner.go:51] Run: sudo systemctl start cri-docker.socket I0815 04:49:31.046115 8106 start.go:450] Will wait 60s for socket path /var/run/cri-dockerd.sock I0815 04:49:31.046193 8106 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0815 04:49:31.050243 8106 start.go:471] Will wait 60s for crictl version I0815 04:49:31.050281 8106 exec_runner.go:51] Run: sudo crictl version I0815 04:49:31.054754 8106 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0815 04:49:42.103141 8106 exec_runner.go:51] Run: sudo crictl version I0815 04:49:42.108156 8106 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0815 04:50:03.716087 8106 exec_runner.go:51] Run: sudo crictl version I0815 04:50:03.721371 8106 retry.go:31] will retry after 26.202601198s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0815 04:50:29.924201 8106 exec_runner.go:51] Run: sudo crictl version I0815 04:50:29.933369 8106 out.go:177] W0815 04:50:29.935459 8106 out.go:239] X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found

W0815 04:50:29.935487 8106 out.go:239] W0815 04:50:29.936429 8106 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0815 04:50:29.938295 8106 out.go:177]

Operating System

No response

Driver

No response

RA489 commented 2 years ago

/kind support

klaases commented 2 years ago

Hi @umeshsoni2, have you tried installing crictl?

From the logs:

sudo: crictl: command not found
I0815 04:49:42.103141 8106 exec_runner.go:51] Run: sudo crictl version
I0815 04:49:42.108156 8106 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found
I0815 04:50:03.716087 8106 exec_runner.go:51] Run: sudo crictl version
I0815 04:50:03.721371 8106 retry.go:31] will retry after 26.202601198s: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found
I0815 04:50:29.924201 8106 exec_runner.go:51] Run: sudo crictl version
I0815 04:50:29.933369 8106 out.go:177]
W0815 04:50:29.935459 8106 out.go:239] X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found
klaases commented 1 year ago

Hi @umeshsoni2 – is this issue still occurring? Are additional details available? If so, please feel free to re-open the issue by commenting with /reopen. This issue will be closed as additional information was unavailable and some time has passed.

Additional information that may be helpful:

Thank you for sharing your experience!