Running minikube on minikube

[afbjorklund]

Some users want to use minikube as their container environment, instead of Docker Desktop.

Then they want to use this VM, to run Kubernetes inside a container - with the KIC driver.

Maybe this "double install" could be made simpler, than the current three step process:

minikube start --no-kubernetes --vm --container-runtime=docker --profile=machine
eval $(minikube -p machine docker-env)
minikube start --driver docker --container-runtime=containerd

Basically using Docker Toolbox (docker-machine), instead of Docker Desktop. And then kind.

docker-machine create machine -d virtualbox --virtualbox-cpu-count 2 --virtualbox-memory 2048
eval $(docker-machine env machine)
kind create cluster

---

Docker have recently updated their product subscriptions, for the proprietary Docker Desktop.

Kubernetes 1.24 is going to replace "docker" with "containerd", as the (blue) container runtime:

References:

• https://en.wikipedia.org/wiki/Turducken
• https://www.imdb.com/title/tt1375666/

[afbjorklund]

There was an article from Matt Rickard on Docker Desktop alternatives:

https://matt-rickard.com/docker-desktop-alternatives/

Unfortunately it didn't mention the preferred minikube driver: "docker".
Or that the "hyperkit" driver uses the old Docker code (based on xhyve).

The main problem being that neither it (HyperKit) nor VirtualBox runs on ARM.
So we would need a "new" driver based on QEMU, to replace the old ones.

[afbjorklund]

I should mention here that Docker Toolbox is not supported anymore.
And that it doesn't work out of the box (no tunneling) with kind, either.

Those projects were just used as reference, since they share some code.
They now refer to using Docker Desktop, as the replacement for the others.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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 and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten