aki-k

@berryscone No, I don't work for Microsoft. Now that Microsoft and Canonical created WSL, they should make it work as well as they can without artificial limitations. Here's the command...

@parapilot I wrote about the automatic WSL 2 start at system startup for both Windows service method and for Task Scheduler method here: https://github.com/microsoft/WSL/issues/9231#issuecomment-1715312138 https://github.com/microsoft/WSL/issues/9231#issuecomment-1718985779

@imsir0vic The fix for the WSL 2 instance auto-shutdown is to start it like this: ``` wsl.exe --distribution Ubuntu-22.04 --exec dbus-launch true & wsl.exe --distribution Ubuntu-22.04 ```

This problem still occurs with the registry.fedoraproject.org/fedora:42 image (the solution is the same chmod 600 /etc/shadow).

@valankar wrote: > Has anyone really tested distrobox with docker? Yes, I use distrobox with docker and the bug was there with the registry.fedoraproject.org/fedora:42 image

After joining two other VMs to the swarm, the ingress network configuration on the second and third VM include those "Containers" and "Peers" keys , but the "Peers" configuration is...

@geek-at Sorry I didn't find a solution for that.

@arrmo I was able to resolve that problem by doing this: https://github.com/microsoft/WSL/issues/8835#issuecomment-1446474057 Edit: I've enabled systemd in WSL by using this: https://github.com/DamionGans/ubuntu-wsl2-systemd-script (The enabler script still works, but on newer...

@joes Yes

Now I'm not so sure any more if my WSL is from the Store: ``` PS C:\Windows\system32> Get-AppxPackage | findstr /i "linux" Name : MicrosoftCorporationII.WindowsSubsystemForLinux PackageFullName : MicrosoftCorporationII.WindowsSubsystemForLinux_1.1.3.0_x64__8wekyb3d8bbwe InstallLocation :...