Hello, when i am using WSL2, the setup is painfull...
# docker
b
Hello, when i am using WSL2, the setup is painfully slow. It even runs into timeouts. Compared to this, my working WSL1 is much faster. I am using Ubuntu 20.04 LTS, installed docker-compose and dockerForWindows is setup to use WSL2, has experimental Features on, as well as "buildkit". The sourcecode is not hosted inside the WSL-Machine. So what am i doing wrong here?
p
what are the specs of your machine?
What exactly do you mean by saying the sourcecode is not hosted in the WSL machine?
b
i7-8850H, 32GB, Win10 Pro 2004 - 19041.508 WSL receives 12GB and 8 cores, no swap The sourcecode is accessed by /mnt/d/....
p
By setup you mean
docker/sdk up
?
b
yes. Composer is really slow and comparing the NodsJS-Installing i can see, that WSL2 is 10x slower than WSL1 and thus runs in to multiple timeouts Even the setup of the containers gets stuck, because docker-compose is not found anymore oO
docker-sdk is 1.21.0
Spryker-B2C 202001
p
that is odd. I have experienced some very strange behavior with docker for desktop though, too. What has helped in the past is using absolute latest docker for desktop. Edge Version
b
hm... i haven't used the edge version yet... i can give it a try...
p
It not always helps, and i have not seen the problems you are having, yet, but it has sorted out some problems in the past. Might be worth a try
Also, corporate AV and the likes might also be a factor
b
wouldn't that also interfer with the wsl1 setup?
from the changelog of docker-edge i don't think it will help
p
AV related issues are pretty much a black box and i have seen all kinds of strange things happening that nobody could explain.
Just the process of elimination, right?
b
yep
p
i can confirm though, that this is not a general issue, since wls2 + docker runs well on my machine
b
and i am one of the "lucky"-ones, that can use WSL1 😂
p
never got WSL1 to work on my machine, so yes, you are lucky, indeed 🙂
b
hm... AV is silent and doesn't do anything... but i also got a small container running with windows-cmd and not an wsl-machine and it seems... i have general problems with wsl2 😞
i have looked a bit. This seems to be a general problem, when the files are not stored inside the WSL2-Container 😞
f
This general problem with wsl2: https://github.com/microsoft/WSL/issues/4197
I use Kali-GUI from Windows. I installed phpstorm (in Kali) and checked out spryker (in my user home at Kali). That works and I have no performance problems.

https://www.youtube.com/watch?v=nXThnFxwH9câ–¾

it is important that spryker code is no longer in windows mount (/mnt/*)
s
so the solution could be opening project from
\\wsl$
drive (which exists inside Linux) In this case the application will work on the full speed, but PhpStorm will work with the files using network file system, which is OK.
BTW @full-morning-49835 thanks for the link, this is really great comment https://github.com/microsoft/WSL/issues/4197#issuecomment-604592340