Minikube + Containerd driver?

[shinebayar-g]

What Happened?

Hi. Does Minikube support containerd as a standalone driver? It's mentioned as one of the possible runtimes, but not driver.
I was wondering if Minikube could support containerd as a driver alternative for Docker.

Attach the log file

N/A

Operating System

macOS (Default)

Driver

Docker

[afbjorklund]

Minikube supports Docker and Podman, but not containerd. Neither does kind, with the same type of arguments:

• containerd / nerdctl provider support kubernetes-sigs/kind#2317

The standard now is running containerd-in-docker, with crio-in-podman as some kind of experimental alternative...

Support cri-dockerd (for runtime) and supporting nerdctl (for driver) is becoming more of a maintenance burden.

[shinebayar-g]

Thanks for the answer. Container based options are not looking good.. Podman is experimental and Docker is restricted with license changes. Looks like I should look into other VM based alternatives for the time being.

[afbjorklund]

Especially the minikube docker-env is hard to support in the long run, even if we have a short term workaround.

There are also more people using Docker Desktop and Podman Desktop, instead of the more open alternatives.
It is possible to use Rancher Desktop for better containerd support, but then the default is to use k3s instead.

[afbjorklund]

Podman is experimental and Docker is restricted with license changes.

Note that there are no license changes for Docker Engine, it is still Open Source. Same goes for Podman Engine.

[shinebayar-g]

Yeah but that's only available on Linux OS right?

[afbjorklund]

Minikube uses Docker Machine, for the others.

[shinebayar-g]

I am confused. What does that mean? How can I use that if I don't have Docker desktop installed on my MacOS for example?

❯ minikube start --driver=docker
😄  [minikube-v1.25] minikube v1.32.0 on Darwin 14.2.1 (arm64)
🆕  Kubernetes 1.28.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.28.3
✨  Using the docker driver based on existing profile

💣  Exiting due to PROVIDER_DOCKER_NOT_RUNNING: "docker version --format <no value>-<no value>:<no value>" exit status 1: Cannot connect to the Docker daemon at unix:///Users/home/.docker/run/docker.sock. Is the docker daemon running?
💡  Suggestion: Start the Docker service
📘  Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/

[afbjorklund]

As you mention, it is mostly used as the runtime for the Kubernetes cluster. Not as the engine for the node.

But in theory it is possible to run minikube-in-minikube, just that it is not a primary setup (out-of-the-box)

minikube start --vm --no-kubernetes (for podman it would be crio runtime)

https://minikube.sigs.k8s.io/docs/tutorials/docker_desktop_replacement/

[k8s-triage-robot]

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-triage-robot]

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-triage-robot]

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:

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

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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:

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

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

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

/close not-planned

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-sigs/prow repository.