-
Notifications
You must be signed in to change notification settings - Fork 274
-
Notifications
You must be signed in to change notification settings - Fork 274
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
RD on Windows #15
Comments
FWIW, Docker on Windows (when on Windows 10 Home) only runs via WSL2; there it appears to act like nested containers — it runs a Microsoft-shipped Linux kernel, and each distribution gets their own chroot / pid namespace (but appears to have a shared network namespace). They also have a HyperV backend, but HyperV is only available on Pro+ Windows licenses. |
@mook-as k3s runs in linux under WSLv2. The questions will be... which Linux do we use and why? Is it a separate one from the users or right in a users linux setup? How do we install and how do we bridge k8s to Windows? We can't use Hyper-V because running in Windows Home is a priority. |
The deliverable for this issue is the WSL/k3s setup that can later be connected to the app/UI via #147 |
I've written up instructions as part of the release notes for tinyk3s-v0.1. I intend to tweak this setup further in the future, but it should be good enough to get started with RD for now. Maybe try all the steps manually once, to verify that they are working on other machines beside my VM? And let me know if I missed to explain some scenario! Since we don't have an init system like systemd under WSL, we'll need to do some monitoring/restarting at the RD level, but I assume that is outside the scope of this issue. |
I've get as foar as Also, I didn't bother with the shell script - I just downloaded files manually and put them in the right places. Suggestions, for later:
|
Notes on getting a RD dev environment on Windows: Dependencies:
With that, I may have missed stuff; feel free to edit this comment to update the instructions. |
Closing, because things landed and WSL-based RD should work now (with lots of polish needed). |
…ring-shutdown-containerd Allow containerd port binding removal after shutdown
…ring-shutdown-containerd Allow containerd port binding removal after shutdown
…tegration-proxy Add a proxy for wsl integration
We need to have RD running on Windows and that includes Windows Home where there is no hypervisor. Instead of a normal hypervisor we should use Windows Subsystem for Linux (likely v2). WSL is available on Windows 10 Home.
With WSL we could either install and manage k3s in an existing Linux or start up a custom Linux setup and expose K3s to windows and the other Linux instances from there. This is open for discussion.
This isn't going to use Minikube as minikube on Windows doesn't work with WSL to manage the things.
The text was updated successfully, but these errors were encountered: