search

kubernetes / minikube

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

cri-docker.service - CRI Interface for Docker Application Container Engine Failed #16799

Closed amrit07nara closed 8 months ago

amrit07nara commented 1 year ago

What Happened?

sudo minikube start --vm-driver=none

X Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker: exit status 1 stdout:

stderr: Job for cri-docker.service failed because the control process exited with error code. See "systemctl status cri-docker.service" and "journalctl -xe" for details.

root@ip-172-31-83-61:/usr/local/bin# systemctl status cri-docker.service ● cri-docker.service - CRI Interface for Docker Application Container Engine Loaded: loaded (/etc/systemd/system/cri-docker.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/cri-docker.service.d └─10-cni.conf Active: failed (Result: exit-code) since Fri 2023-06-30 17:22:09 UTC; 1min 25s ago TriggeredBy: ● cri-docker.socket Docs: https://docs.mirantis.com Process: 5658 ExecStart=/usr/local/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=registry.k8s.io/pause:3.9 --network-pl> Main PID: 5658 (code=exited, status=1/FAILURE)

Jun 30 17:22:09 ip-172-31-83-61 systemd[1]: cri-docker.service: Scheduled restart job, restart counter is at 3. Jun 30 17:22:09 ip-172-31-83-61 systemd[1]: Stopped CRI Interface for Docker Application Container Engine. Jun 30 17:22:09 ip-172-31-83-61 systemd[1]: cri-docker.service: Start request repeated too quickly. Jun 30 17:22:09 ip-172-31-83-61 systemd[1]: cri-docker.service: Failed with result 'exit-code'. Jun 30 17:22:09 ip-172-31-83-61 systemd[1]: Failed to start CRI Interface for Docker Application Container Engine.

Attach the log file

stderr: I0630 17:28:59.000660 5684 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet I0630 17:28:59.013093 5684 fix.go:103] recreateIfNeeded on minikube: state=Stopped err= W0630 17:28:59.013110 5684 fix.go:129] unexpected machine state, will restart: I0630 17:28:59.015853 5684 out.go:177] Restarting existing none bare metal machine for "minikube" ... I0630 17:28:59.019192 5684 profile.go:148] Saving config to /root/.minikube/profiles/minikube/config.json ... I0630 17:28:59.019347 5684 start.go:300] post-start starting for "minikube" (driver="none") I0630 17:28:59.019393 5684 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] I0630 17:28:59.019433 5684 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 I0630 17:28:59.028130 5684 main.go:141] libmachine: Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found I0630 17:28:59.028152 5684 main.go:141] libmachine: Couldn't set key VERSION_CODENAME, no corresponding struct field found I0630 17:28:59.028165 5684 main.go:141] libmachine: Couldn't set key UBUNTU_CODENAME, no corresponding struct field found I0630 17:28:59.031169 5684 out.go:177] OS release is Ubuntu 20.04.6 LTS I0630 17:28:59.033263 5684 filesync.go:126] Scanning /root/.minikube/addons for local assets ... I0630 17:28:59.033315 5684 filesync.go:126] Scanning /root/.minikube/files for local assets ... I0630 17:28:59.033341 5684 start.go:303] post-start completed in 13.984017ms I0630 17:28:59.033350 5684 fix.go:57] fixHost completed within 63.663382ms I0630 17:28:59.033357 5684 start.go:83] releasing machines lock for "minikube", held for 63.687057ms I0630 17:28:59.033749 5684 exec_runner.go:51] Run: sh -c "stat /etc/cni/net.d/loopback.conf" I0630 17:28:59.033871 5684 exec_runner.go:51] Run: curl -sS -m 2 https://registry.k8s.io/ W0630 17:28:59.035826 5684 cni.go:208] loopback cni configuration skipped: "/etc/cni/net.d/loopback.conf" not found I0630 17:28:59.035866 5684 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" ; I0630 17:28:59.045636 5684 cni.go:258] no active bridge cni configs found in "/etc/cni/net.d" - nothing to disable I0630 17:28:59.045652 5684 start.go:481] detecting cgroup driver to use... I0630 17:28:59.045677 5684 detect.go:196] detected "cgroupfs" cgroup driver on host os I0630 17:28:59.045776 5684 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///run/containerd/containerd.sock " | sudo tee /etc/crictl.yaml" I0630 17:28:59.064889 5684 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" W0630 17:28:59.076145 5684 start.go:448] 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 I0630 17:28:59.076170 5684 start.go:481] detecting cgroup driver to use... I0630 17:28:59.076197 5684 detect.go:196] detected "cgroupfs" cgroup driver on host os I0630 17:28:59.076395 5684 exec_runner.go:51] Run: /bin/bash -c "sudo mkdir -p /etc && printf %!s(MISSING) "runtime-endpoint: unix:///var/run/cri-dockerd.sock " | sudo tee /etc/crictl.yaml" I0630 17:28:59.095352 5684 exec_runner.go:51] Run: which cri-dockerd I0630 17:28:59.096298 5684 exec_runner.go:51] Run: sudo mkdir -p /etc/systemd/system/cri-docker.service.d I0630 17:28:59.104219 5684 exec_runner.go:144] found /etc/systemd/system/cri-docker.service.d/10-cni.conf, removing ... I0630 17:28:59.104230 5684 exec_runner.go:207] rm: /etc/systemd/system/cri-docker.service.d/10-cni.conf I0630 17:28:59.104310 5684 exec_runner.go:151] cp: memory --> /etc/systemd/system/cri-docker.service.d/10-cni.conf (195 bytes) I0630 17:28:59.104440 5684 exec_runner.go:51] Run: sudo cp -a /tmp/minikube2443376820 /etc/systemd/system/cri-docker.service.d/10-cni.conf I0630 17:28:59.112704 5684 exec_runner.go:51] Run: sudo systemctl unmask docker.service I0630 17:28:59.342869 5684 exec_runner.go:51] Run: sudo systemctl enable docker.socket I0630 17:28:59.568088 5684 docker.go:538] configuring docker to use "cgroupfs" as cgroup driver... I0630 17:28:59.568115 5684 exec_runner.go:144] found /etc/docker/daemon.json, removing ... I0630 17:28:59.568142 5684 exec_runner.go:207] rm: /etc/docker/daemon.json I0630 17:28:59.568211 5684 exec_runner.go:151] cp: memory --> /etc/docker/daemon.json (144 bytes) I0630 17:28:59.568359 5684 exec_runner.go:51] Run: sudo cp -a /tmp/minikube12454852 /etc/docker/daemon.json I0630 17:28:59.580626 5684 exec_runner.go:51] Run: sudo systemctl daemon-reload I0630 17:28:59.900085 5684 exec_runner.go:51] Run: sudo systemctl restart docker I0630 17:29:00.225149 5684 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0630 17:29:00.464294 5684 exec_runner.go:51] Run: sudo systemctl unmask cri-docker.socket I0630 17:29:00.717327 5684 exec_runner.go:51] Run: sudo systemctl enable cri-docker.socket I0630 17:29:00.969918 5684 exec_runner.go:51] Run: sudo systemctl daemon-reload I0630 17:29:01.199678 5684 exec_runner.go:51] Run: sudo systemctl restart cri-docker.socket I0630 17:29:01.217638 5684 exec_runner.go:51] Run: sudo systemctl daemon-reload I0630 17:29:01.453513 5684 exec_runner.go:51] Run: sudo systemctl restart cri-docker I0630 17:29:01.541473 5684 out.go:177] W0630 17:29:01.544289 5684 out.go:239] X Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker: exit status 1 stdout:

stderr: Job for cri-docker.service failed because the control process exited with error code. See "systemctl status cri-docker.service" and "journalctl -xe" for details.

W0630 17:29:01.544319 5684 out.go:239] W0630 17:29:01.545514 5684 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯ I0630 17:29:01.551933 5684 out.go:177]

Operating System

Ubuntu

Driver

None

afbjorklund commented 1 year ago

See "systemctl status cri-docker.service" and "journalctl -xe" for details.