Issue with minkube driver=none #15780
Comments
|
You need to install all the requirements, such as |
afbjorklund
added
co/none-driver
kind/support
|
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-ci-robot
added
the
lifecycle/stale
|
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-ci-robot
added
lifecycle/rotten
|
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-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What Happened?
minikube start --vm-driver=none
😄 minikube v1.29.0 on Ubuntu 18.04 (amd64)
✨ Using the none driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing none bare metal machine for "minikube" ...
ℹ️ OS release is Ubuntu 18.04.6 LTS
❌ 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.txtand attach logs.txt to the GitHub issue.Attach the log file
I0203 15:16:37.421253 14198 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf"
W0203 15:16:37.426344 14198 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found
I0203 15:16:37.426441 14198 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d
I0203 15:16:37.436689 14198 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (135 bytes)
I0203 15:16:37.436824 14198 exec_runner.go:51] Run: sudo cp -a /tmp/minikube1792449395 /etc/systemd/system/cri-docker.service.d/10-cni.conf
I0203 15:16:37.446342 14198 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 15:16:37.458860 14198 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable
I0203 15:16:37.458925 14198 start.go:483] detecting cgroup driver to use...
I0203 15:16:37.458974 14198 detect.go:196] detected "cgroupfs" cgroup driver on host os
I0203 15:16:37.459145 14198 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 15:16:37.488173 14198 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 15:16:37.501066 14198 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 15:16:37.501086 14198 start.go:483] detecting cgroup driver to use...
I0203 15:16:37.501116 14198 detect.go:196] detected "cgroupfs" cgroup driver on host os
I0203 15:16:37.501281 14198 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 15:16:37.523947 14198 exec_runner.go:51] Run: sudo systemctl unmask docker.service
I0203 15:16:37.720974 14198 exec_runner.go:51] Run: sudo systemctl enable docker.socket
I0203 15:16:37.932189 14198 docker.go:529] configuring docker to use "cgroupfs" as cgroup driver...
I0203 15:16:37.932236 14198 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (144 bytes)
I0203 15:16:37.932422 14198 exec_runner.go:51] Run: sudo cp -a /tmp/minikube2191531857 /etc/docker/daemon.json
I0203 15:16:37.942845 14198 exec_runner.go:51] Run: sudo systemctl daemon-reload
I0203 15:16:38.145157 14198 exec_runner.go:51] Run: sudo systemctl restart docker
I0203 15:16:38.605636 14198 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket
I0203 15:16:38.801056 14198 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket
I0203 15:16:38.998054 14198 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket
I0203 15:16:39.205343 14198 exec_runner.go:51] Run: sudo systemctl daemon-reload
I0203 15:16:39.409219 14198 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket
I0203 15:16:39.430372 14198 start.go:530] Will wait 60s for socket path /var/run/cri-dockerd.sock
I0203 15:16:39.430601 14198 exec_runner.go:51] Run: stat /var/run/cri-dockerd.sock
I0203 15:16:39.433332 14198 start.go:551] Will wait 60s for crictl version
I0203 15:16:39.433398 14198 exec_runner.go:51] Run: which crictl
I0203 15:16:39.437591 14198 out.go:177]
W0203 15:16:39.441060 14198 out.go:239] ❌ Exiting due to RUNTIME_ENABLE: which crictl: exit status 1
stdout:
Operating System
Ubuntu
Driver
None
The text was updated successfully, but these errors were encountered: