Open dantesun opened 2 years ago
Thanks for the report! Hmm.. possibly this is the same issue as https://github.com/nullpo-head/wsl-distrod/issues/9 Could you share the information about your environment?
Environment
- Windows Version: [output of
winver
on Windows]- Linux kernel version [output of
uname -a
on any WSL distro]- Distro version [e.g. "Ubuntu 20.04" ]
Could you also share the result of the this, please?
To check whether Systemd crashes or not, could you share the result of ps aux after Distrod crashes, by
wsl -e ps aux
command? The name of the systemd process is like/sbin/init ....setenv=...
it systemd exists, could you share the output ofwsl -e ls /proc/[pid of the systemd you found]/ns
as well, please?
I
I just had seemingly the same log output on a fresh Windows+WSL. It turned out even though I think wsl --status
said default version 2, new distros were created with version 1.
It turned out even though I think wsl --status said default version 2, new distros were created with version 1.
Well, I hadn't thought of that. Some other issues also seem to be this problem. Thanks for your information @pelepelin !
Describe the bug A clear and concise description of what the bug is. Executing
wsl
has no effect. It exits without any message.Logs Please share the output of the trace logs, following the reference