this post was submitted on 29 Jun 2023
817 points (96.5% liked)

linuxmemes

21387 readers
1307 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    817
    When WSL2 first came out, some losers on /g/ were cheering that it would "make Linux obsolete". Four years later, I think it's safe to say they were kinda missing the point. (vlemmy.net)
    submitted 1 year ago by [email protected] to c/linuxmemes
    128 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] jmanes 11 points 1 year ago (2 children)

    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.

    [–] [email protected] 8 points 1 year ago

    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.

    [–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

    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 2 points 1 year ago* (last edited 1 year ago) (1 children)

    I've been using Linux for 15 years. Tinkering 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 that I can hack it just enough to work (sometimes), but it is nothing like using Linux natively.

    [–] [email protected] 0 points 1 year ago

    To be clear I wasn't trying to say WSL replaces Linux. Just trying to help with your issues. I use WSL on Windows but I still also use native Arch (btw).