-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL2 systemd integration does not work (Windows 11) #9313
Comments
Ah it appears you need to run Ubuntu 22.04 to use the WSL/systemd integration... I don't recall seeing the Ubuntu version requirement mentioned in the docs or the introduction blog post for this feature: https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/ . I was able to get systemd working once I launched a 22.04 VM. Is this feature supposed to work seamlessly in older Ubuntu releases that are still in the Microsoft Store or just 22.04+? |
@plombardi89: systemd should be supported in older distros as well, as long as you're using Store WSL If you're still seeing the issue with older distributions, please share /logs |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
Version
Microsoft Windows [Version 10.0.22621.819]
WSL Version
Kernel Version
5.15.79.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
/etc/wsl.conf
wsl --shutdown
(also performed a full system restart during debug attempts)Expected Behavior
I expected systemd to be running as PID 1 and
systemctl
to be able to successfully query the state of services.Actual Behavior
Diagnostic Logs
dmesg:
The text was updated successfully, but these errors were encountered: