never had problems of systemd/2 minutes delays
not sure what would be the correct test here, but:
root@LP-T16:~# uname -rn
LP-T16 5.15.167.4-microsoft-standard-WSL2
root@LP-T16:~# time systemctl restart ssh
real 0m0.039s
user 0m0.008s
sys 0m0.001s
never had problems of systemd/2 minutes delays
not sure what would be the correct test here, but:
root@LP-T16:~# uname -rn
LP-T16 5.15.167.4-microsoft-standard-WSL2
root@LP-T16:~# time systemctl restart ssh
real 0m0.039s
user 0m0.008s
sys 0m0.001s
The delay is related to starting WSL 2, not starting a systemd service btw.
Maybe it's specific to Windows 10 Pro, who knows. I'm using the latest WSL 2 from the MS app store.
I just know when I installed Docker directly into WSL 2, when I launched a terminal I could not run `docker info` and connect to the Docker daemon for 2 minutes. The culprit was the Docker service was not available. I was able to reproduce this on Arch and Ubuntu distros.
Separate to that systemd also delayed a terminal from opening for ~15 seconds (unrelated to Docker).
After ~10 minutes of the terminal being closed, both issues happened. They went away as soon as I disabled systemd.
First opening of my main wsl2 Ubuntu 22.04 instance takes roughly 20 seconds, the next new terminals opens in ~1s. As it happens once a 3 weeks or so when Windows rebooted for updates, I don't care much.
It takes me more time to fill passwords for ssh keys to agent anyways.
Granted, I'm not using native docker inside.