systemd Not Booting Up in WSL 2 Despite Configuration in wsl.conf

[owlcode3]

Windows Version

Microsoft Windows [Version 10.0.21996.1]

WSL Version

WSL 2

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu-22.04

Other Software

No response

Repro Steps

1. Install WSL and Ubuntu 22.04:

• Followed the official WSL installation guide to install WSL 2 and the Ubuntu 22.04 distribution.

2. Configure wsl.conf:

• Edited the /etc/wsl.conf file to include the following configuration:

[boot] systemd=true

3. Restart WSL:

• Executed the following command in PowerShell as an administrator to shut down WSL:

wsl --shutdown

4. Start WSL and Verify systemd:

• Opened the Ubuntu terminal and ran:

ps -p 1 -o comm=

Expected Behavior

The command should output systemd, indicating that systemd is running as the init system.

Actual Behavior

The output is not systemd, and running systemctl status returns the following error:

System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

Diagnostic Logs

No response

Tasks

Preview Give feedback

No tasks being tracked yet.

[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.79
• Systemd not starting correctly on fresh install after reboot (#9207), similarity score: 0.79

Closed similar issues:

• Distro not booting with systemd enabled (#9850), similarity score: 0.83
• systemd no longer boots (#10557), similarity score: 0.81
• Systemctl not working as expected (#10428), similarity score: 0.79

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

[owlcode3]

I can't get the log

[OneBlue]

Closing since this issue doesn't have logs

[owlcode3]

Here I've collected the logs as requested.
WslLogs-2024-06-12_11-52-06.zip

Steps to reproduce the issue:

1. Set the default WSL version to 2: wsl --set-default-version 2
2. Attempt to start WSL: wsl
3. Check the status of systemd: systemctl status
4. sudo systemctl status snapd

The error message encountered was: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Appx package is not installed
Found no WSL traces in the logs

[owlcode3]

I've edited my last comment to include the new log file as requested. Please let me know if there are any further details needed.

[owlcode3]

Can this issue be reopen? I’ve added the log as requested

[owlcode3]

@OneBlue please can you reopen the issue as I've provided the log as requested

[toshydev]

If you open the wsl.conf with vim, what is the format showing in the bottom left corner?
If it's showing [dos] you need to convert it to UNIX format by using a tool like dos2unix or by deleting and rewriting it inside the wsl with vim or nano.