I work at Oracle and leverage WSL for for some things. It works… but I wish I could just use Linux. WSL is full of gotchas and weird bugs. Performance is not good either.
WSL2 is essentially a VM, and doesn’t seem to have any weird bugs or gotcha’s anymore (at least for command line programs). I don’t use it for work, but playing around with it as a hobby, it seems fairly solid.
I use WSL2. It has bugs. DNS stops working when you connect to a VPN, which I have to do every day for all of my work. To fix that you can either modify the resolv conf (which gets wiped out on every startup) and then chattr it to prevent it from being deleted (this still didn’t quite work for me). Or you can install wsl-vpnkit and pipe all of your network traffic through another container.
I have been working in docker and rancher desktop, both of which have integrations with WSL but with other caviats and bugs. I basically have a bunch of very highly specific steps written up for other employees for “how to get this working with WSL” because it is so buggy.
I feel so vinticated reading somebody else going through the DNS hell WSL2+VPN DNS issues. It is a nightmare in professional environments and for the life of me I cannot get my resolv to stop reverting after a while. Thanks for the tip on wsl-vpnkit, much harder to convince VM teams to spin you up a remote dev environment than to just use WSL sometimes.
Tinkering around to get things working is a part of the authentic Linux experience. Performance is 95% to Ubuntu 20.0.4 so not sure what you mean by that. resolv.conf won’t get wiped out if you put
[networking]generateResolvConf = false
in your /etc/wsl.conf file.
A more modern solution is outlined here which you will want to adjust if you’re using something other than Cisco.
I work at Oracle and leverage WSL for for some things. It works… but I wish I could just use Linux. WSL is full of gotchas and weird bugs. Performance is not good either.
WSL2 is essentially a VM, and doesn’t seem to have any weird bugs or gotcha’s anymore (at least for command line programs). I don’t use it for work, but playing around with it as a hobby, it seems fairly solid.
I use WSL2. It has bugs. DNS stops working when you connect to a VPN, which I have to do every day for all of my work. To fix that you can either modify the resolv conf (which gets wiped out on every startup) and then chattr it to prevent it from being deleted (this still didn’t quite work for me). Or you can install wsl-vpnkit and pipe all of your network traffic through another container.
I have been working in docker and rancher desktop, both of which have integrations with WSL but with other caviats and bugs. I basically have a bunch of very highly specific steps written up for other employees for “how to get this working with WSL” because it is so buggy.
I feel so vinticated reading somebody else going through the DNS hell WSL2+VPN DNS issues. It is a nightmare in professional environments and for the life of me I cannot get my resolv to stop reverting after a while. Thanks for the tip on wsl-vpnkit, much harder to convince VM teams to spin you up a remote dev environment than to just use WSL sometimes.
Tinkering around to get things working is a part of the authentic Linux experience. Performance is 95% to Ubuntu 20.0.4 so not sure what you mean by that. resolv.conf won’t get wiped out if you put
[networking] generateResolvConf = falsein your /etc/wsl.conf file.
A more modern solution is outlined here which you will want to adjust if you’re using something other than Cisco.
I use WSL2 a lot and it does have weird “uniquenesses”.