You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using a custom wsl2 kernel with bridge and openvswitch configured as KO.
I can load the module in any distro by creating a link in /lib/modules that points to the wsl2 modules directory. It works just fine.
But some KOs need to be loaded at the beginning, for example, the bridge module which is a requirement of docker desktop.
If I didn't load bridge in default distro, the docker desktop can't start.
Since all distros shared the same kernel, I think it's wsl's responsibility to load kernel modules at the boot time.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm using a custom wsl2 kernel with bridge and openvswitch configured as KO.
I can load the module in any distro by creating a link in /lib/modules that points to the wsl2 modules directory. It works just fine.
But some KOs need to be loaded at the beginning, for example, the bridge module which is a requirement of docker desktop.
If I didn't load bridge in default distro, the docker desktop can't start.
Since all distros shared the same kernel, I think it's wsl's responsibility to load kernel modules at the boot time.
Beta Was this translation helpful? Give feedback.
All reactions