this post was submitted on 21 Jun 2023
497 points (99.2% liked)

linuxmemes

21198 readers
319 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!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    497
    wsl (lemmy.world)
    submitted 1 year ago by Linuxmemed to c/linuxmemes
    50 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] netwren 5 points 1 year ago (3 children)

    Ugh yeah the networking on wsl2 has been annoying me lately.

    [–] [email protected] 7 points 1 year ago (3 children)

    Getting WSL2 to work with my company's VPN was such a pain that I just went back to WSL1 and resigned myself to the fact that I'll never be able to run Docker in WSL locally.

    [–] linearchaos 1 points 1 year ago

    You probably just need to shuffle the network pri and fix the nameservers. I took a couple of days and sorted it out.

    You only need to shuffle the weights once, but you need to manually fix the ns every time.

    [–] keyez 1 points 1 year ago

    Don't want to be that works on my machine person but I use docker-ce installed in my WSL2 VM and can push and pull over my companies' openvpn running on windows.

    [–] netwren 1 points 1 year ago (1 children)

    Why not just run a full Hypervisor?

    [–] riodoro1 9 points 1 year ago* (last edited 1 year ago) (3 children)

    Why not just run full Linux?

    [–] baronvonj 5 points 1 year ago

    Why not Bilbo?

    [–] PutangInaMo 2 points 1 year ago

    Linux hypervisor?

    [–] timewarp 1 points 1 year ago

    This right here. Using Podman natively on Linux is beautiful.

    [–] [email protected] 3 points 1 year ago (1 children)

    What about it has been annoying or caused problems? I ask so I won't be surprised if it happens to me.

    [–] netwren 10 points 1 year ago

    So WSL1 was actually using the Windows Kernel so Networking was more straightforward because you had direct access to network syscalls.

    WSL2 is a VM in HyperV with some special sauce I guess. Downside is that means you have the same Network setup like you would a VPN.

    So when I'm developing a site and use say trunk serve. I can access it locally on my Windows browser even though it's running on my debian WSL2. However one thing I liked to do on my local network was pull up my smartphone and open ports to look at the mobile view on an actual mobile browser.

    Well now open ports in Windows Advfirewall for a service that's running a Linux VM?

    Now do this everytime your WSL2 VM changes it's local IP (not your LAN IP), and everytime you switch to a service with a different port.

    Super PITA and I also broke just the regular local proxy between Windows-WSL2 trying to get it working. So now I just sigh and use the developer tools in Chrome to pretend I'm on a smartphone.