Blue
Blue
That's surprising. Could you capture logs WSL failing to start after updating the file access ?
Hmm OK then I can think of two other things that would cause this: 1) Does your user account also have full access to the parent folder ? 2) Is...
@CatalinFetoiu: Looks like WSL's mirrored networking port range is conflicting with docker. Maybe we should increase the range here ?
Thank you all for reporting this ! To give an update, the issue is indeed #2595. WSL1 currently doesn't implement TCGETS2, which causes packages built on glibc 2.42 to fail...
Thank you for reporting this @StrixLake. Looking at the logs, I can see that WSL is getting access denied when trying to open the disks: ``` Microsoft.Windows.HyperV.Worker FallbackError 11-14-2024 21:45:42.850...
Ok interesting. Could you share which permissions you have the drive's root folders ?
Looking at the logs, it looks like the distribution VHDX was already in use by someone else. Did you use wsl --mount on that disk, or did another program access...
Interesting. Sadly the docker diagnostic ID don't help me since I don't have access to those. To root cause this we'd need logs from a repro so we can see...
Thank you @VaanaraRaaja. Looking at the logs, I can see the issue still seems to indeed be memory: ``` 53986 False Microsoft.Windows.Lxss.Manager GuestLog 0 06-04-2025 18:44:02.392 " " "text: ""[...
> Nope, did not help. I am now trying to install from source after i built the docker. Since it was too frustrating running the docker full build again and...