-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add support for VM-free deployments using Docker #4389
Comments
Do we really have to write multiple implementations, or can we use something like CRI from the start ? Like https://kind.sigs.k8s.io/docs/design/principles#target-cri-functionality (and to avoid that extra work) |
See this kind Dockerfile for some of the crazy stuff needed, when running systemd in a container: This issue (VM-free deployments) is likely to have to work with changes to libmachine and buildroot... The "none" driver isn't really a VM-free environment, it's just intended to run on a pre-allocated VM. This issue is different, since it doesn't require the user to do anything but provide a container runtime. That is something else than installing the kubelet on the local host. It also allows for multiple nodes. |
See also https://github.com/kubernetes/community/blob/master/contributors/design-proposals/cluster-lifecycle/local-cluster-ux.md for the original minikube proposal and some of the reasoning behind it... |
@medyagh : will you run a sshd in the "node" container, or should we use exec and nsenter instead ? I was wondering about the |
I would user exec, which will invoke "docker exec" I am implementing a specialized commander for the vm-free which is basically a helper for docker exec |
This feature is expected to be done by next quarter. |
the undocumented support for docker vm driver has been merged by #6151 I will close this issue and make smaller issues to be tracked for next steps of kic |
This will give a much better user experience for folks in nested VM's than the "none" driver currently provides.
If possible, this should be done in collaboration with the fine folks at https://github.com/kubernetes-sigs/kind
The text was updated successfully, but these errors were encountered: