kubernetes/minikube

none with containerd: make it possible to run without the `docker` CLI

Open

#10,908 opened on Mar 24, 2021

View on GitHub
 (23 comments) (0 reactions) (0 assignees)Go (5,222 forks)batch import
co/none-driverco/runtime/containerdhelp wantedkind/buglifecycle/frozenpriority/backlog

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

Steps to reproduce the issue:

This is the current behavior regarding initizliation with none driver with containerd runtime.

# minikube start --driver=none --container-runtime='containerd'
😄  minikube v1.18.1 on Ubuntu 20.04 (amd64)
✨  Using the none driver based on user configuration

🤷  Exiting due to PROVIDER_NONE_NOT_FOUND: The 'none' provider was not found: exec: "docker": executable file not found in $PATH
💡  Suggestion: Install docker
📘  Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/none/

root@minikube:~# minikube start -h | grep provider
root@minikube:~# minikube start --driver=none --container-runtime='containerd'
😄  minikube v1.18.1 on Ubuntu 20.04 (amd64)
✨  Using the none driver based on user configuration

🤷  Exiting due to PROVIDER_NONE_NOT_FOUND: The 'none' provider was not found: exec: "docker": executable file not found in $PATH
💡  Suggestion: Install docker
📘  Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/none/

Since Docker is no longer default runtime, I think even none driver should consider the runtime option if specified.

Full output of failed command:

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

Contributor guide