systemd not running in my Debian distro even though enabled in /etc/wsl.conf and running in my Ubuntu distro

[mwoodpatrick]

Windows Version

Microsoft Windows [Version 10.0.22631.3672]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-microsoft-standard-WSL2

Distro Version

Debian GNU/Linux 12 (bookworm)

Other Software

No response

Repro Steps

Install wsl-2 through windows store
install Debian distro (wsl --install Debian)
start Debian (wsl -d Debian)
Add following to /etc/wsl,conf

[boot]
systemd=true

shutdown and restart wsl:

wsl --shutdown
wsl -d Debian
systemctl status
     

Expected Behavior

systemd is running in my Debian distro just as it is in my Ubuntu distro

Actual Behavior

systemctl status reports

Failed to connect to bus: No such file or directory

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down (#8883), similarity score: 0.76

Closed similar issues:

• [PID 1 Error] "failed to connect to bus: no such file or directory" Windows 10, WSL 2, Debian - possible fix detailed (#10350), similarity score: 0.77
• Systemctl not working as expected (#10428), similarity score: 0.75
• Distro not booting with systemd enabled (#9850), similarity score: 0.75
• No systemd support on Windows DevKit 2023 (#9094), similarity score: 0.74

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[mwoodpatrick]

My problem, systemd is running, closing