kubernetes / minikube

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

issue in starting minikube #15004

Closed sasigowda closed 1 year ago

sasigowda commented 2 years ago

What Happened?

*

stderr: I0923 02:30:06.812367 7800 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0923 02:30:06.825187 7800 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0923 02:30:06.825203 7800 fix.go:129] unexpected machine state, will restart: I0923 02:30:06.827037 7800 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0923 02:30:06.831717 7800 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0923 02:30:06.831821 7800 start.go:300] post-start starting for "minikube" (driver="none") I0923 02:30:06.831868 7800 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] I0923 02:30:06.831917 7800 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 I0923 02:30:06.843547 7800 main.go:134] libmachine: Couldn't set key CPE_NAME, no corresponding struct field found I0923 02:30:06.845668 7800 out.go:177] OS release is Amazon Linux 2 I0923 02:30:06.847619 7800 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0923 02:30:06.847677 7800 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0923 02:30:06.847700 7800 start.go:303] post-start completed in 15.864042ms I0923 02:30:06.847709 7800 fix.go:57] fixHost completed within 50.013926ms I0923 02:30:06.847716 7800 start.go:83] releasing machines lock for "minikube", held for 50.036878ms I0923 02:30:06.848212 7800 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ I0923 02:30:06.848231 7800 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" I0923 02:30:06.876342 7800 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0923 02:30:06.964973 7800 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0923 02:30:07.047560 7800 exec_runner.go:51] Run: sudo systemctl daemon-reload I0923 02:30:07.134884 7800 exec_runner.go:51] Run: sudo systemctl restart docker I0923 02:30:08.045919 7800 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0923 02:30:08.150198 7800 exec_runner.go:51] Run: sudo systemctl daemon-reload I0923 02:30:08.237593 7800 exec_runner.go:51] Run: sudo systemctl start cri-docker.socket I0923 02:30:08.250997 7800 start.go:450] Will wait 60s for socket path /var/run/cri-dockerd.sock I0923 02:30:08.251068 7800 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0923 02:30:08.254038 7800 start.go:471] Will wait 60s for crictl version I0923 02:30:08.254086 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:08.260981 7800 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:30:19.307881 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:19.314940 7800 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:30:40.926136 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:40.933279 7800 retry.go:31] will retry after 26.202601198s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:31:07.136385 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:31:07.145544 7800 out.go:177] W0923 02:31:07.147037 7800 out.go:239] X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found

W0923 02:31:07.147062 7800 out.go:239] W0923 02:31:07.148205 7800 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0923 02:31:07.150039 7800 out.go:177]

*

Attach the log file

*

stderr: I0923 02:30:06.812367 7800 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0923 02:30:06.825187 7800 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0923 02:30:06.825203 7800 fix.go:129] unexpected machine state, will restart: I0923 02:30:06.827037 7800 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0923 02:30:06.831717 7800 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0923 02:30:06.831821 7800 start.go:300] post-start starting for "minikube" (driver="none") I0923 02:30:06.831868 7800 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] I0923 02:30:06.831917 7800 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 I0923 02:30:06.843547 7800 main.go:134] libmachine: Couldn't set key CPE_NAME, no corresponding struct field found I0923 02:30:06.845668 7800 out.go:177] OS release is Amazon Linux 2 I0923 02:30:06.847619 7800 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0923 02:30:06.847677 7800 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0923 02:30:06.847700 7800 start.go:303] post-start completed in 15.864042ms I0923 02:30:06.847709 7800 fix.go:57] fixHost completed within 50.013926ms I0923 02:30:06.847716 7800 start.go:83] releasing machines lock for "minikube", held for 50.036878ms I0923 02:30:06.848212 7800 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ I0923 02:30:06.848231 7800 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" I0923 02:30:06.876342 7800 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0923 02:30:06.964973 7800 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0923 02:30:07.047560 7800 exec_runner.go:51] Run: sudo systemctl daemon-reload I0923 02:30:07.134884 7800 exec_runner.go:51] Run: sudo systemctl restart docker I0923 02:30:08.045919 7800 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0923 02:30:08.150198 7800 exec_runner.go:51] Run: sudo systemctl daemon-reload I0923 02:30:08.237593 7800 exec_runner.go:51] Run: sudo systemctl start cri-docker.socket I0923 02:30:08.250997 7800 start.go:450] Will wait 60s for socket path /var/run/cri-dockerd.sock I0923 02:30:08.251068 7800 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0923 02:30:08.254038 7800 start.go:471] Will wait 60s for crictl version I0923 02:30:08.254086 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:08.260981 7800 retry.go:31] will retry after 11.04660288s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:30:19.307881 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:19.314940 7800 retry.go:31] will retry after 21.607636321s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:30:40.926136 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:30:40.933279 7800 retry.go:31] will retry after 26.202601198s: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found I0923 02:31:07.136385 7800 exec_runner.go:51] Run: sudo crictl version I0923 02:31:07.145544 7800 out.go:177] W0923 02:31:07.147037 7800 out.go:239] X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1 stdout:

stderr: sudo: crictl: command not found

W0923 02:31:07.147062 7800 out.go:239] W0923 02:31:07.148205 7800 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0923 02:31:07.150039 7800 out.go:177]

*

Operating System

Other

Driver

No response

RA489 commented 1 year ago

/kind support

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 and PRs.

This bot triages issues and PRs 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/15004#issuecomment-1461231324): >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.