• communistcapy@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    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.

    • jmanes@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I’ve been using Linux for 15 years. Tinking with WSL is not as fruitful as tinkering with Linux.

      The link you provided for DNS is exactly the solution I was describing in my original post. It never worked for me, though. We have a custom DNS setup in-house and simply setting the nameserver doesn’t work. It is far too much of a hassle, so we just spin up wsl-vpnkit when we need network access.

      Mac users and Linux native users don’t have these issues and everything works out of the box.

      The performance I get when compiling and running integration tests through Rancher desktop integration on WSL is abysmal. Taking 30+ minutes to complete whereas for other employees on Macs see things done in under 5 minutes. Not sure if there is a WSL specific firewall / networking issue or what. If you look up “WSL2 poor network performacne” you’ll see dozens of open GitHub issues. It is very non-deterministic. Some days it runs great, other days it is terrible.

      I assume I’ll have a million of other replies coming along that link me to random benchmarks and articles about how great WSL2 is, but I’m telling you, I use it every single day at my job as a software engineer. It has problems. I’m grateful it exists and you can hack it just enough to work (sometimes), but it is nothing like using Linux natively.