-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Description
Docker Machine is not really a thing anymore, and the code was archived more than 5 years ago:
https://github.com/docker-archive-public/docker.machine
%description
Minikube uses Docker Machine to manage the Kubernetes VM so it benefits
from the driver plugin architecture that Docker Machine uses to provide
a consistent way to manage various VM providers.
Now it is part of minikube, and can be referred to as either libmachine or perhaps minikube-machine:
https://github.com/minikube-machine/machine
require github.com/docker/machine v0.16.2
replace github.com/docker/machine => github.com/minikube-machine/machine
Provisioning a machine with Docker on does not really help with running modern Kubernetes*.
Since it uses different container runtimes, such as containerd (with nerdctl) or cri-o (with podman).
Providing a Docker API for the node is better done on top of containerd, as an optional add-on:
https://docs.docker.com/engine/storage/containerd/ (from /var/lib/docker to /var/lib/containerd)
Similar to how you can access the CRI-O images with Podman, but the containers are kept separate?
Normally you would not run any containers that way, but only use it for loading and building images.
Eventually libmachine could be refactored to just be an internal implementation detail of minikube...
And then the minikube-machine organization could be retired, along with the no longer used drivers?
* well, you could use Docker to run Kubernetes in. But that's not really the primary project goal?
I meant docker as a container runtime for Kubernetes, which has been fading out ever since 1.24.