search

kubernetes / minikube

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

Error on running `minikube start --vm-driver=none` as root #15779

Closed Qwestuha closed 1 year ago

Qwestuha commented 1 year ago

Что произошло?

при запуске получаю ошибку sudo minikube start --vm-driver=none

Приложите логи

root@evgeniy-VirtualBox:/home/evgeniy/cri-dockerd# cat logs.txt *

stderr: I0203 14:26:57.481742 7841 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0203 14:26:57.507702 7841 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0203 14:26:57.507714 7841 fix.go:129] unexpected machine state, will restart: I0203 14:26:57.510860 7841 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0203 14:26:57.516711 7841 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0203 14:26:57.516929 7841 start.go:300] post-start starting for "minikube" (driver="none") I0203 14:26:57.517032 7841 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] I0203 14:26:57.517141 7841 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 I0203 14:26:57.535546 7841 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0203 14:26:57.535579 7841 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0203 14:26:57.535600 7841 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0203 14:26:57.561162 7841 out.go:177] OS release is Linux Mint 20.3 I0203 14:26:57.563681 7841 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0203 14:26:57.587869 7841 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0203 14:26:57.588401 7841 start.go:303] post-start completed in 71.460291ms I0203 14:26:57.588413 7841 fix.go:57] fixHost completed within 159.469904ms I0203 14:26:57.588420 7841 start.go:83] releasing machines lock for "minikube", held for 159.497488ms I0203 14:26:57.589142 7841 exec_runner.go:51] Run: cat /version.json W0203 14:26:57.620761 7841 start.go:396] Unable to open version.json: cat /version.json: exit status 1 stdout:

stderr: cat: /version.json: No such file or directory I0203 14:26:57.620841 7841 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" I0203 14:26:57.620845 7841 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0203 14:26:57.654344 7841 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0203 14:26:57.654456 7841 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0203 14:26:57.683043 7841 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes) I0203 14:26:57.683637 7841 exec_runner.go:51] Run: sudo cp -a /tmp/minikube2327445496 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0203 14:26:57.709876 7841 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" ; I0203 14:26:57.803721 7841 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0203 14:26:57.803742 7841 start.go:483] detecting cgroup driver to use... I0203 14:26:57.803778 7841 detect.go:196] detected "cgroupfs" cgroup driver on host os I0203 14:26:57.804078 7841 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" I0203 14:26:57.870027 7841 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" W0203 14:26:57.893978 7841 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 I0203 14:26:57.893998 7841 start.go:483] detecting cgroup driver to use... I0203 14:26:57.894076 7841 detect.go:196] detected "cgroupfs" cgroup driver on host os I0203 14:26:57.894300 7841 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" I0203 14:26:57.944544 7841 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0203 14:26:58.610212 7841 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0203 14:26:59.255046 7841 docker.go:529] configuring docker to use "cgroupfs" as cgroup driver... I0203 14:26:59.255108 7841 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (144 bytes) I0203 14:26:59.255533 7841 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1589769627 /etc/docker/daemon.json I0203 14:26:59.291749 7841 exec_runner.go:51] Run: sudo systemctl daemon-reload I0203 14:26:59.893671 7841 exec_runner.go:51] Run: sudo systemctl restart docker I0203 14:27:02.152421 7841 exec_runner.go:84] Completed: sudo systemctl restart docker: (2.2586726s) I0203 14:27:02.152537 7841 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0203 14:27:02.781449 7841 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0203 14:27:03.422035 7841 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0203 14:27:04.027125 7841 exec_runner.go:51] Run: sudo systemctl daemon-reload I0203 14:27:04.647698 7841 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0203 14:27:04.686964 7841 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock I0203 14:27:04.687116 7841 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock I0203 14:27:04.694657 7841 start.go:551] Will wait 60s for crictl version I0203 14:27:04.694753 7841 exec_runner.go:51] Run: which crictl I0203 14:27:04.701044 7841 out.go:177] W0203 14:27:04.703457 7841 out.go:239] X Exiting due to RUNTIME_ENABLE: which crictl: exit status 1 stdout:

stderr:

W0203 14:27:04.703507 7841 out.go:239] W0203 14:27:04.710279 7841 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0203 14:27:04.712927 7841 out.go:177]

Операционная система

Ubuntu

Драйвер

Docker

IlyshaNil commented 1 year ago

Do you install crictl?

sftim commented 1 year ago

/retitle Error on running minikube start --vm-driver=none as root

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/15779#issuecomment-1634813797): >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.