-
Notifications
You must be signed in to change notification settings - Fork 829
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
WSL2: dockerd related missing kernel flags #4165
Comments
I can confirm that adding missing flags makes it possible to run swarm and netwoking seems to work.
|
(it does also that for xt_conntrack) |
Thanks @simonferquel, I will make sure all those config options get added to the kernel config. Since the kernel that we are using for WSL2 includes modules statically instead of in a separate folder those warnings are benign. It would likely be good to add a flag to docker daemon to suppress those errors for WSL2. |
That is what I suspected. |
@simonferquel - Yes, I will add that as well. If that is needed, should it be added to the check-config script? |
@simonferquel The WSL-ed Linux kernel source here https://thirdpartysource.microsoft.com/download/Windows%20Subsystem%20for%20Linux%20v2/May%202019/WSLv2-Linux-Kernel-master.zip. Found the kernel configs at |
Yep already working on it for starting prototyping Kubernetes enabled integration packs
…________________________________
From: Biswapriyo Nath <notifications@github.com>
Sent: Monday, June 17, 2019 8:52:29 PM
To: microsoft/WSL
Cc: Simon Ferquel; Mention
Subject: Re: [microsoft/WSL] WSL2: dockerd related missing kernel flags (#4165)
@simonferquel<https://github.com/simonferquel> The WSL-ed Linux kernel source here https://thirdpartysource.microsoft.com/download/Windows%20Subsystem%20for%20Linux%20v2/May%202019/WSLv2-Linux-Kernel-master.zip. Found the kernel configs at WSLv2-Linux-Kernel-master\Microsoft\config-wsl.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#4165?email_source=notifications&email_token=AAMZQFNBVO4GG6AFSDHQH4TP27MOZA5CNFSM4HYVPCFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4DSTI#issuecomment-502806861>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAMZQFLD3ZBPE53DZ45ZET3P27MOZANCNFSM4HYVPCFA>.
|
You can get that at runtime with:
Which is a nice touch, since we don't have |
Will this issue fix the VXLAN issue? I'am getting this when trying to use networl overlays in Docker Swarm |
@MortenRickiRasmussen yes. I have a built a kernel with a modified kconfig file, and I can expose ports on the ingress network, create and attach to overlay networks etc. |
Related to this is that Kubernetes needs |
@simonferquel Can you mention which configs you have changed? |
You can use the diff tool in the kernel sources script directory to look at the changes
…________________________________
From: Biswapriyo Nath <notifications@github.com>
Sent: Friday, June 28, 2019 5:15:25 PM
To: microsoft/WSL
Cc: Simon Ferquel; Mention
Subject: Re: [microsoft/WSL] WSL2: dockerd related missing kernel flags (#4165)
@simonferquel<https://github.com/simonferquel> Can you mention which configs you have changed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#4165?email_source=notifications&email_token=AAMZQFLLEBYJD7FSTZA4XJTP4YTI3A5CNFSM4HYVPCFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2LM3Q#issuecomment-506771054>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAMZQFJX7Z6HRI2GA5JWR73P4YTI3ANCNFSM4HYVPCFA>.
|
Hello, Plese see weaveworks/ignite#129 . My guess is that the issue is somewhat related to Woud you please consider enabling it for the next release ? |
@andrelop You can compile your own kernel and place it in System32\lxss\tools folder. We don't have to wait for next builds. |
Or compile it as a module, in which case you don't need to muck lxss/tools. |
Hello
Reproducing here what I posted at weaveworks/ignite#129 to see if you could help with the correct procedure to build/use a custom kernel for a given WSL2 VM : I tried building a custom kernel but the WSL2 VM cannot start after I change the C:\Windows\System32\lxss\tools\kernel using the vmlinux kernel produced by the kernel build process. What I did :
Not sure what else I could try or if what I did was really what needed to be done. |
@andrelop The renamed kernel that works for me is arch/x86/boot/bzImage which is 7Mb in size. edit: Since there is no Microsoft folder in that v4.19.57.tar.gz file it will be better to download the WSL2 kernel from https://github.com/microsoft/WSL2-Linux-Kernel/archive/master.zip |
@simonferquel - where's your modified kconfig? |
@PatrickLang wsl kernel config is updated with those flags. See the commit on Jul 21, 2019. |
I think this works now |
May I know how to use this insider build kernel? As I am trying to run docker on surface pro X wsl2 I seems come across the issue on iptable support of the kernel as well. |
The kernel has been available for the general public for a while, you're most probably using nftables on Debian or Ubuntu. Otherwise, you can check the following link: docs.microsoft.com/en-us/windows/wsl/install-win10 sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy |
By running https://github.com/moby/moby/blob/master/contrib/check-config.sh within wsl2, I just produced a report of missing things for running dockerd with all features enabled:
cc @benhillis, I think it should help.
I'll try to make my own kernel with all this setup accordingly, and will do experiment to setup kubernetes in a similar way as what we do in Docker Desktop to see how things go.
The text was updated successfully, but these errors were encountered: