Skip to content
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

No systemd support on Windows DevKit 2023 #9094

Closed
1 of 2 tasks
Gerdya opened this issue Oct 31, 2022 · 9 comments
Closed
1 of 2 tasks

No systemd support on Windows DevKit 2023 #9094

Gerdya opened this issue Oct 31, 2022 · 9 comments

Comments

@Gerdya
Copy link

Gerdya commented Oct 31, 2022

Version

10.0.22623.875

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.15.68.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

I did a fresh install on my newly delivered Windows DevKit 2023 as follows:

Powershell:
wsl --install (which installed WSL2 and Ubuntu 20.04)

inside Ubuntu:
sudo do-release-upgrade -d (which did upgrade to 22.04)

inside Ubuntu:
create /etc/wsl.conf with:
[boot]
systemd=true

wsl --shutdown

Expected Behavior

xxxx@DevKit:/etc$ systemctl
Failed to connect to bus: No such file or directory

Actual Behavior

systemctl works

Diagnostic Logs

Please let me know if you need more information.

@Biswa96
Copy link

Biswa96 commented Oct 31, 2022

You have to install WSL Preview from Windows Store.

@NotTheDr01ds
Copy link

NotTheDr01ds commented Oct 31, 2022

@Biswa96 Hmmm. Maybe, maybe not.

Under Windows 11 22H2 (22621) wsl --install automatically installs the latest Preview release directly from the Store unless you specifically tell it not to with wsl --install --inbox. The OP is using an Insider build later than 22H2 (22623), so it should behave the same. See my notes on this in #8975 - I tested and confirmed this behavior myself. However, I haven't gone back and confirmed that 0.70.0 (current latest) is currently being installed. Regardless, a wsl --update should move to a Systemd-capable release.

Side-note: WSL1 isn't even installed with a base wsl --install under 22H2.

So @Gerdya, can you confirm your WSL release using wsl --version and/or wsl --status? If wsl --version just returns help text, then Biswa96 is right and you'll need to separately install a Preview release from the Store.

@Gerdya
Copy link
Author

Gerdya commented Oct 31, 2022

I have the following versions installed:
wsl --version
WSL version: 0.70.5.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22623.875

wsl --status
Default Distribution: Ubuntu
Default Version: 2
WSL1 is not supported with your current machine configuration.
Please enable the "Windows Subsystem for Linux" optional component to use WSL1.

Note: I do have precisely the same WSL version ( 0.70.5.0) on my Surface Pro X, where systemd works.

@elsaco
Copy link

elsaco commented Oct 31, 2022

systemd works on DevKit 2023. Test was done using Debian but it should work with any other Ubuntu distros also:

WSL version: 0.70.5.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.169

and sample systemctl output:

tux@dragon:~$ systemctl status user.slice
● user.slice - User and Session Slice
     Loaded: loaded (/lib/systemd/system/user.slice; static)
     Active: active since Mon 2022-10-31 15:49:41 PDT; 29s ago
       Docs: man:systemd.special(7)
      Tasks: 0
     Memory: 0B
     CGroup: /user.slice

Output of gcim win32_baseboard:

Manufacturer : Microsoft Corporation
Model        :
Name         : Base Board
SerialNumber : <deleted>
SKU          :
Product      : Windows Dev Kit 2023

In your case Failed to connect to bus: No such file or directory means you need to add dbus package and reboot.

@OneBlue
Copy link
Collaborator

OneBlue commented Nov 1, 2022

/logs

@ghost
Copy link

ghost commented Nov 1, 2022

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:

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

Thank you!

@ghost ghost added the needs-author-feedback label Nov 1, 2022
@Gerdya
Copy link
Author

Gerdya commented Nov 1, 2022

I did created logs:

  1. start logging
  2. start wsl/ubuntu
  3. stop logging

WslLogs-2022-11-01_10-12-26.zip

@ghost ghost removed the needs-author-feedback label Nov 1, 2022
@OneBlue
Copy link
Collaborator

OneBlue commented Nov 4, 2022

Thank you @Gerdya.

Looking at the logs, it looks like /sbin/init just failed to start on your ubuntu distribution.

Can share the output of ps aux, ls -la /proc/1/fd and dmesg inside ubuntu ?

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants