search

kubernetes / minikube

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

Issue when I start minikube start #16037

Closed satishlap143 closed 9 months ago

satishlap143 commented 1 year ago

What Happened?

root@test-server:~# minikube start

stderr: find: ‘/etc/cni/net.d’: No such file or directory

X Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

╭─────────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

root@test-server:~# cat log.txt *

stderr: I0313 17:01:53.995360 16222 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0313 17:01:54.126915 16222 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0313 17:01:54.126984 16222 fix.go:129] unexpected machine state, will restart: I0313 17:01:54.131952 16222 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0313 17:01:54.142465 16222 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0313 17:01:54.143665 16222 start.go:300] post-start starting for "minikube" (driver="none") I0313 17:01:54.144033 16222 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] I0313 17:01:54.144273 16222 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 I0313 17:01:54.264047 16222 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0313 17:01:54.264168 16222 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0313 17:01:54.264227 16222 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0313 17:01:54.269354 16222 out.go:177] OS release is Ubuntu 22.04.2 LTS I0313 17:01:54.273656 16222 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0313 17:01:54.273868 16222 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0313 17:01:54.274040 16222 start.go:303] post-start completed in 130.272512ms I0313 17:01:54.274099 16222 fix.go:57] fixHost completed within 1.514521627s I0313 17:01:54.274153 16222 start.go:83] releasing machines lock for "minikube", held for 1.514661628s I0313 17:01:54.276513 16222 exec_runner.go:51] Run: cat /version.json I0313 17:01:54.277962 16222 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0313 17:01:54.286923 16222 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0313 17:01:54.287132 16222 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" W0313 17:01:54.304424 16222 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0313 17:01:54.305397 16222 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0313 17:01:54.425670 16222 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0313 17:01:54.425761 16222 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0313 17:01:54.425990 16222 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0313 17:01:54.426833 16222 exec_runner.go:51] Run: sudo cp -a /tmp/minikube3171763730 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0313 17:01:54.562267 16222 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" ; E0313 17:01:54.673824 16222 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 I0313 17:01:54.674201 16222 start.go:483] detecting cgroup driver to use... I0313 17:01:54.674342 16222 detect.go:199] detected "systemd" cgroup driver on host os I0313 17:01:54.676346 16222 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" I0313 17:01:54.930396 16222 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" I0313 17:01:55.053397 16222 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" I0313 17:01:55.233389 16222 containerd.go:145] configuring containerd to use "systemd" as cgroup driver... I0313 17:01:55.233598 16222 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )SystemdCgroup = .$|\1SystemdCgroup = true|g' /etc/containerd/config.toml" I0313 17:01:55.399429 16222 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" I0313 17:01:55.519411 16222 exec_runner.go:51] Run: sh -c "sudo sed -i '/systemd_cgroup/d' /etc/containerd/config.toml" I0313 17:01:55.646130 16222 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runc.v1"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0313 17:01:55.777320 16222 exec_runner.go:51] Run: sh -c "sudo rm -rf /etc/cni/net.mk" I0313 17:01:55.895587 16222 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" I0313 17:01:56.030921 16222 exec_runner.go:51] Run: sudo sysctl net.bridge.bridge-nf-call-iptables I0313 17:01:56.148511 16222 exec_runner.go:51] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" I0313 17:01:56.280008 16222 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:01:58.599606 16222 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.319452668s) I0313 17:01:58.599886 16222 exec_runner.go:51] Run: sudo systemctl restart containerd I0313 17:01:59.321479 16222 start.go:483] detecting cgroup driver to use... I0313 17:01:59.321634 16222 detect.go:199] detected "systemd" cgroup driver on host os I0313 17:01:59.322229 16222 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" I0313 17:02:00.632537 16222 exec_runner.go:84] Completed: /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": (1.310191087s) I0313 17:02:00.632750 16222 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0313 17:02:02.928150 16222 exec_runner.go:84] Completed: sudo systemctl unmask docker.service: (2.295236469s) I0313 17:02:02.928347 16222 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0313 17:02:05.273098 16222 exec_runner.go:84] Completed: sudo systemctl enable docker.socket: (2.344619945s) I0313 17:02:05.273157 16222 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0313 17:02:05.273249 16222 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0313 17:02:05.273297 16222 exec_runner.go:207] rm: /etc/docker/daemon.json I0313 17:02:05.273434 16222 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0313 17:02:05.274122 16222 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1637709340 /etc/docker/daemon.json I0313 17:02:05.380601 16222 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:02:07.639974 16222 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.258886113s) I0313 17:02:07.640562 16222 exec_runner.go:51] Run: sudo systemctl restart docker I0313 17:02:10.468459 16222 exec_runner.go:84] Completed: sudo systemctl restart docker: (2.827778806s) I0313 17:02:10.468688 16222 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0313 17:02:12.761300 16222 exec_runner.go:84] Completed: sudo systemctl enable cri-docker.socket: (2.292302444s) I0313 17:02:12.761539 16222 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0313 17:02:16.032369 16222 exec_runner.go:84] Completed: sudo systemctl unmask cri-docker.socket: (3.270713594s) I0313 17:02:16.032584 16222 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0313 17:02:18.214994 16222 exec_runner.go:84] Completed: sudo systemctl enable cri-docker.socket: (2.181870592s) I0313 17:02:18.215197 16222 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:02:20.515977 16222 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.300689757s) I0313 17:02:20.516083 16222 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0313 17:02:20.725547 16222 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0313 17:02:20.725974 16222 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0313 17:02:20.738889 16222 start.go:551] Will wait 60s for crictl version I0313 17:02:20.739104 16222 exec_runner.go:51] Run: which crictl I0313 17:02:20.758154 16222 out.go:177] W0313 17:02:20.761695 16222 out.go:239] X Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

W0313 17:02:20.762795 16222 out.go:239] W0313 17:02:20.767766 16222 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0313 17:02:20.775839 16222 out.go:177]

Operating System

Ubuntu

Driver

VirtualBox

satishlap143 commented 1 year ago

Please help what I need to done for this issue

afbjorklund commented 1 year ago

You need to install all requirements: docker, cri-dockerd, cri-tools, cni-plugins

satishlap143 commented 1 year ago

After Installing still I`m facing same issue.........

satishlap143 commented 1 year ago

root@test-server:~# cat logs.tx *

stderr: I0313 17:34:55.458321 18969 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0313 17:34:55.574056 18969 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0313 17:34:55.574124 18969 fix.go:129] unexpected machine state, will restart: I0313 17:34:55.579650 18969 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0313 17:34:55.593866 18969 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0313 17:34:55.594917 18969 start.go:300] post-start starting for "minikube" (driver="none") I0313 17:34:55.595684 18969 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] I0313 17:34:55.595886 18969 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 I0313 17:34:55.704319 18969 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0313 17:34:55.704428 18969 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0313 17:34:55.704497 18969 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0313 17:34:55.710672 18969 out.go:177] OS release is Ubuntu 22.04.2 LTS I0313 17:34:55.715890 18969 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0313 17:34:55.716339 18969 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0313 17:34:55.716921 18969 start.go:303] post-start completed in 121.865512ms I0313 17:34:55.717014 18969 fix.go:57] fixHost completed within 1.455326273s I0313 17:34:55.717077 18969 start.go:83] releasing machines lock for "minikube", held for 1.455558702s I0313 17:34:55.719491 18969 exec_runner.go:51] Run: cat /version.json I0313 17:34:55.720375 18969 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0313 17:34:55.730246 18969 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0313 17:34:55.730605 18969 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" W0313 17:34:55.749184 18969 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0313 17:34:55.749787 18969 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0313 17:34:55.861926 18969 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0313 17:34:55.862002 18969 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0313 17:34:55.862309 18969 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0313 17:34:55.863289 18969 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1280885004 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0313 17:34:55.977620 18969 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" ; E0313 17:34:56.093857 18969 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 I0313 17:34:56.094050 18969 start.go:483] detecting cgroup driver to use... I0313 17:34:56.094148 18969 detect.go:199] detected "systemd" cgroup driver on host os I0313 17:34:56.094684 18969 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" I0313 17:34:56.327802 18969 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" I0313 17:34:56.439300 18969 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" I0313 17:34:56.565710 18969 containerd.go:145] configuring containerd to use "systemd" as cgroup driver... I0313 17:34:56.566019 18969 exec_runner.go:51] Run: sh -c "sudo sed -i -r 's|^( )SystemdCgroup = .$|\1SystemdCgroup = true|g' /etc/containerd/config.toml" I0313 17:34:56.683201 18969 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" I0313 17:34:56.795428 18969 exec_runner.go:51] Run: sh -c "sudo sed -i '/systemd_cgroup/d' /etc/containerd/config.toml" I0313 17:34:56.934140 18969 exec_runner.go:51] Run: sh -c "sudo sed -i 's|"io.containerd.runc.v1"|"io.containerd.runc.v2"|g' /etc/containerd/config.toml" I0313 17:34:57.237750 18969 exec_runner.go:51] Run: sh -c "sudo rm -rf /etc/cni/net.mk" I0313 17:34:57.410729 18969 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" I0313 17:34:57.573243 18969 exec_runner.go:51] Run: sudo sysctl net.bridge.bridge-nf-call-iptables I0313 17:34:57.676885 18969 exec_runner.go:51] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" I0313 17:34:57.786680 18969 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:35:00.159941 18969 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.373006998s) I0313 17:35:00.160293 18969 exec_runner.go:51] Run: sudo systemctl restart containerd I0313 17:35:00.750641 18969 start.go:483] detecting cgroup driver to use... I0313 17:35:00.750761 18969 detect.go:199] detected "systemd" cgroup driver on host os I0313 17:35:00.751791 18969 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" I0313 17:35:02.016596 18969 exec_runner.go:84] Completed: /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": (1.264676165s) I0313 17:35:02.017732 18969 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0313 17:35:04.351041 18969 exec_runner.go:84] Completed: sudo systemctl unmask docker.service: (2.333082883s) I0313 17:35:04.351353 18969 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0313 17:35:06.571078 18969 exec_runner.go:84] Completed: sudo systemctl enable docker.socket: (2.219591671s) I0313 17:35:06.571140 18969 docker.go:529] configuring docker to use "systemd" as cgroup driver... I0313 17:35:06.571222 18969 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0313 17:35:06.571268 18969 exec_runner.go:207] rm: /etc/docker/daemon.json I0313 17:35:06.571432 18969 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (143 bytes) I0313 17:35:06.572179 18969 exec_runner.go:51] Run: sudo cp -a /tmp/minikube2165633860 /etc/docker/daemon.json I0313 17:35:06.718050 18969 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:35:09.021087 18969 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.302758107s) I0313 17:35:09.021365 18969 exec_runner.go:51] Run: sudo systemctl restart docker I0313 17:35:12.806174 18969 exec_runner.go:84] Completed: sudo systemctl restart docker: (3.784709386s) I0313 17:35:12.806468 18969 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0313 17:35:15.055265 18969 exec_runner.go:84] Completed: sudo systemctl enable cri-docker.socket: (2.248654853s) I0313 17:35:15.055505 18969 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0313 17:35:17.376350 18969 exec_runner.go:84] Completed: sudo systemctl unmask cri-docker.socket: (2.320709713s) I0313 17:35:17.376574 18969 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0313 17:35:20.753238 18969 exec_runner.go:84] Completed: sudo systemctl enable cri-docker.socket: (3.376550149s) I0313 17:35:20.753481 18969 exec_runner.go:51] Run: sudo systemctl daemon-reload I0313 17:35:23.219800 18969 exec_runner.go:84] Completed: sudo systemctl daemon-reload: (2.466208279s) I0313 17:35:23.220036 18969 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0313 17:35:23.389534 18969 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0313 17:35:23.390141 18969 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0313 17:35:23.403959 18969 start.go:551] Will wait 60s for crictl version I0313 17:35:23.404633 18969 exec_runner.go:51] Run: which crictl I0313 17:35:23.425163 18969 out.go:177] W0313 17:35:23.429695 18969 out.go:239] X Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

W0313 17:35:23.429978 18969 out.go:239] W0313 17:35:23.436600 18969 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0313 17:35:23.440773 18969 out.go:177]

* root@test-server:~#

satishlap143 commented 1 year ago

Please help me and let me know how to resolve the issue

satishlap143 commented 1 year ago

I`m waiting for an reply please help me

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 9 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 9 months ago

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

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