3 ms·
I just popped open WSL2 on my home desktop and ran "apt install dotnet-sdk-8.0" and it ran perfectly fine? It took maybe 10 seconds to install... 13 packages.
by scruple 3y ago
I just popped open WSL2 on my home desktop and ran "apt install dotnet-sdk-8.0" and it ran perfectly fine? It took maybe 10 seconds to install... 13 packages.
I started playing around with WSL1 shortly after it was released. Lady year, at a new employer (primarily a Windows based shop), I started using WSL2 daily. I have never had to manually kill the WSL process.
I wonder what's so different between our installations and systems to cause our experiences to be so different here.
- switch007 3y agoIt's not just me and my system. Go look at open github issues, some of the most commented, each of which have 1-400+ comments: Jul 2022 https://github.com/microsoft/WSL/issues/8529 https://github.com/microsoft/WSL/issues/8529 "All WSL commands hang (including wsl --shutdown) but WSL is constantly using 30-40% CPU " May 2021 https://github.com/microsoft/WSL/issues/6982 https://github.com/microsoft/WSL/issues/6982 "High CPU usage" Jun 2022 https://github.com/microsoft/WSL/issues/8529 https://github.com/microsoft/WSL/issues/8529 "All WSL commands hang (including wsl --shutdown) but WSL is constantly using 30-40% CPU " Jul 2019 https://github.com/microsoft/WSL/issues/4197 https://github.com/microsoft/WSL/issues/4197 "[wsl2] filesystem performance is much slower than wsl1 in /mnt" Feb 2020 https://github.com/microsoft/WSL/issues/4901 https://github.com/microsoft/WSL/issues/4901 "Very slow network speed on WSL2"
- scruple 3y agoSorry, I didn't mean to imply that it was just you. I definitely believe you and others have the problems you do, we're talking about Microsoft software here.