Skip to content

❌ Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker: Process exited with status 1stderr: Job for cri-docker.service failed because a fatal signal was delivered to the control process. See "systemctl status cri-docker.service" and "journalctl -xe" for details. #16273

@samcurryokee

Description

@samcurryokee

What Happened?

I am trying to start minikube but it keeps on bringing this error even after it previously worked after installing cri-dockerd

Attach the log file

E0408 23:03:52.977326 5390 logs.go:192] command /bin/bash -c "sudo /var/lib/minikube/binaries/v1.26.3/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" failed with error: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.26.3/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:

stderr:
error: stat /var/lib/minikube/kubeconfig: no such file or directory
output: "\n** stderr ** \nerror: stat /var/lib/minikube/kubeconfig: no such file or directory\n\n** /stderr **"

❗ unable to fetch logs for: describe nodes

Operating System

Windows

Driver

Docker

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions