Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exiting due to RUNTIME_ENABLE: Failed to start container runtime: which crictl: Process exited with status 1 #19363

Open
debabmon opened this issue Aug 2, 2024 · 9 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@debabmon
Copy link

debabmon commented Aug 2, 2024

What Happened?

ubuntu@powervm20:~$ minikube start --driver=docker --container-runtime=docker
πŸ˜„ minikube v1.33.1 on Ubuntu 22.04 (ppc64le)
✨ Using the docker driver based on existing profile
πŸ‘ Starting "minikube" primary control-plane node in "minikube" cluster
🚜 Pulling base image v0.0.44 ...
πŸƒ Updating the running docker "minikube" container ...

❌ Exiting due to RUNTIME_ENABLE: Failed to start container runtime: which crictl: Process exited with status 1
stdout:

stderr:

Attach the log file

logs.txt

Operating System

Ubuntu

Driver

None

@T-Lakshmi

This comment was marked as outdated.

@T-Lakshmi
Copy link

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Aug 2, 2024
@afbjorklund
Copy link
Collaborator

afbjorklund commented Aug 4, 2024

docker support for container runtime is completely removed in k8s version v1.24 and is now no longer supported.

Docker is supported through cri-dockerd, and is still the default container runtime in minikube

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2024
@k8s-triage-robot
Copy link

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:

  • 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:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 2, 2024
@T-Lakshmi
Copy link

T-Lakshmi commented Dec 3, 2024

@afbjorklund, Agree. thanks for correcting me.

From the logs below is the error causing to not install minikube.

Exiting due to RUNTIME_ENABLE: Failed to start container runtime: which crictl: Process exited with status 1

This is due to missing crictl which is imissing to install.

@T-Lakshmi
Copy link

@debabmon,
Before Kubernetes 1.24, the support for docker was included with the installation (called "dockershim").

After that, you need to make sure to install all the needed components:
docker, cri-dockerd, cri-tools, cni-plugins

Eventually minikube should be able to "provision" these as well, but right now it does not.

@T-Lakshmi
Copy link

This is duplicate issue of #15914

/triage duplicate
/kind support

@k8s-ci-robot k8s-ci-robot added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Dec 3, 2024
@T-Lakshmi
Copy link

@debabmon,
install the missing components and try to reinstall minikube.
share the update here to proceed further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

5 participants