I use wsl2 now with centos and I don't have any networking or memory allocation issues like the ones you describe. > Ultimately, WSL2 is the attempt to take Li

I use wsl2 now with centos and I don't have any networking or memory allocation issues like the ones you describe. > Ultimately, WSL2 is the attempt to take Linux VM and make it appear like it's not a VM. Maybe it'll get there one day, but due to the got-ya's it's not for me. In my experience, its been pretty great and elegant to work with. I've used it for ~1.5 years so far and they seemed to have broken down a lot of those vm walls to make it seem like some kind of hybrid windows + linux operating system. Doing stuff like 'code .' from within wsl to open the current wsl working dir in the vscode windows gui is pretty neat. And you can also do kind of neat stuff like writing to your windows clipboard from within WSL by running the powershell windows executeable. This is in my wsl .bashrc to do that: function cb () { powershell.exe -command "\$input | set-clipboard" } echo "hello" | cb # write hello to my windows clipboard