search

kubernetes / minikube

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

Unable to install Kubernetes #15898

Closed Hirodari closed 1 year ago

Hirodari commented 1 year ago

What Happened?

minikube start --driver=non

Attach the log file

stderr: I0221 09:55:20.858266 21649 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0221 09:55:20.880732 21649 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0221 09:55:20.880773 21649 fix.go:129] unexpected machine state, will restart: I0221 09:55:21.018185 21649 out.go:177] 🔄 Restarting existing none bare metal machine for "minikube" ... I0221 09:55:21.093757 21649 profile.go:148] Saving config to /home/fredbitenyo/.minikube/profiles/minikube/config.json ... I0221 09:55:21.094084 21649 start.go:300] post-start starting for "minikube" (driver="none") I0221 09:55:21.094448 21649 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] I0221 09:55:21.094631 21649 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 I0221 09:55:21.286667 21649 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0221 09:55:21.286801 21649 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0221 09:55:21.286854 21649 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0221 09:55:21.420695 21649 out.go:177] ℹ️ OS release is Ubuntu 22.04.1 LTS I0221 09:55:22.322608 21649 filesync.go:126] Scanning /home/fredbitenyo/.minikube/addons for local assets ... I0221 09:55:22.368282 21649 filesync.go:126] Scanning /home/fredbitenyo/.minikube/files for local assets ... I0221 09:55:22.368719 21649 start.go:303] post-start completed in 1.274616495s I0221 09:55:22.368740 21649 fix.go:57] fixHost completed within 2.018600756s I0221 09:55:22.368751 21649 start.go:83] releasing machines lock for "minikube", held for 2.018628807s I0221 09:55:22.369947 21649 exec_runner.go:51] Run: cat /version.json W0221 09:55:22.373000 21649 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0221 09:55:22.373280 21649 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" I0221 09:55:22.423741 21649 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0221 09:55:22.445550 21649 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0221 09:55:22.445948 21649 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0221 09:55:22.498245 21649 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0221 09:55:22.498635 21649 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1541956003 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0221 09:55:22.516005 21649 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" ; E0221 09:55:22.533529 21649 start.go:415] unable to disable preinstalled bridge CNI(s): failed to disable all bridge cni configs in "/etc/cni/net.d": 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" ;: exit status 1 stdout:

stderr: find: ‘/etc/cni/net.d’: No such file or directory I0221 09:55:22.533566 21649 start.go:483] detecting cgroup driver to use... I0221 09:55:22.533599 21649 detect.go:199] detected "systemd" cgroup driver on host os I0221 09:55:22.533818 21649 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 09:55:22.653453 21649 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" I0221 09:55:22.926180 21649 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" I0221 09:55:22.964754 21649 containerd.go:145] configuring containerd to use "systemd" as cgroup driver... I0221 09:55:22.964935 21649 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )SystemdCgroup = .$|\1SystemdCgroup = true|g' /etc/containerd/config.toml" I0221 09:55:22.983677 21649 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" I0221 09:55:23.002767 21649 exec_runner.go:51] Run: sh -c "sudo sed -i '/systemd_cgroup/d' /etc/containerd/config.toml" I0221 09:55:23.021989 21649 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runc.v1"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0221 09:55:23.041202 21649 exec_runner.go:51] Run: sh -c "sudo rm -rf /etc/cni/net.mk" I0221 09:55:23.059646 21649 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" I0221 09:55:23.078423 21649 exec_runner.go:51] Run: sudo sysctl net.bridge.bridge-nf-call-iptables I0221 09:55:23.095599 21649 exec_runner.go:51] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" I0221 09:55:23.112187 21649 exec_runner.go:51] Run: sudo systemctl daemon-reload I0221 09:55:24.093398 21649 exec_runner.go:51] Run: sudo systemctl restart containerd I0221 09:55:24.929365 21649 exec_runner.go:84] Completed: curl -sS -m 2 https://registry.k8s.io/: (2.50557794s) W0221 09:55:24.929396 21649 start.go:833] [curl -sS -m 2 https://registry.k8s.io/] failed: curl -sS -m 2 https://registry.k8s.io/: exit status 28 stdout:

stderr: curl: (28) SSL connection timeout W0221 09:55:24.929644 21649 out.go:239] ❗ This bare metal machine is having trouble accessing https://registry.k8s.io W0221 09:55:24.929678 21649 out.go:239] 💡 To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/ I0221 09:55:38.814940 21649 exec_runner.go:84] Completed: sudo systemctl restart containerd: (14.721469199s) I0221 09:55:38.814985 21649 start.go:483] detecting cgroup driver to use... I0221 09:55:38.815066 21649 detect.go:199] detected "systemd" cgroup driver on host os I0221 09:55:38.815641 21649 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 09:55:38.864808 21649 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0221 09:55:39.889442 21649 exec_runner.go:84] Completed: sudo systemctl unmask docker.service: (1.024556787s) I0221 09:55:39.889624 21649 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0221 09:55:41.200484 21649 exec_runner.go:84] Completed: sudo systemctl enable docker.socket: (1.310816326s) I0221 09:55:41.200505 21649 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0221 09:55:41.200561 21649 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0221 09:55:41.200901 21649 exec_runner.go:51] Run: sudo cp -a /tmp/minikube689839538 /etc/docker/daemon.json I0221 09:55:41.452952 21649 exec_runner.go:51] Run: sudo systemctl daemon-reload I0221 09:55:42.311724 21649 exec_runner.go:51] Run: sudo systemctl restart docker I0221 09:56:36.849689 21649 exec_runner.go:84] Completed: sudo systemctl restart docker: (54.520004272s) I0221 09:56:36.849907 21649 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0221 09:56:37.633148 21649 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0221 09:56:38.459799 21649 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0221 09:56:39.342285 21649 exec_runner.go:51] Run: sudo systemctl daemon-reload I0221 09:56:40.123113 21649 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0221 09:56:40.153856 21649 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0221 09:56:40.153998 21649 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0221 09:56:40.157940 21649 start.go:551] Will wait 60s for crictl version I0221 09:56:40.158077 21649 exec_runner.go:51] Run: which crictl I0221 09:56:40.244145 21649 out.go:177] W0221 09:56:40.289250 21649 out.go:239] ❌ Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

W0221 09:56:40.289350 21649 out.go:239] W0221 09:56:40.293988 21649 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 09:56:40.598400 21649 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/15898#issuecomment-1645363793): >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.