[systemd] systemd-sysusers.service fails to start.

[Aerocatia]

Version

Microsoft Windows [Version 10.0.22621.674]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.68

Distro Version

Arch Linux

Other Software

No response

Repro Steps

Start the distro with systemd enabled in wsl.conf.

Expected Behavior

systemd services should be successfully initialized.

Actual Behavior

systemd will start in a degraded state as systemd-sysusers.service will fail to start.

The reason for this failure (with a workaround) is documented here: https://github.com/arkane-systems/genie/wiki/Systemd-units-known-to-be-problematic-under-WSL#systemd-sysusersservice

Diagnostic Logs

No response

[mwoodpatrick]

I'm seeing the similar issue on Fedora37

 wsl --version
WSL version: 0.70.0.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.746

systemctl --failed
  UNIT                     LOAD   ACTIVE SUB    DESCRIPTION
● systemd-sysusers.service loaded failed failed Create System Users
● systemd-oomd.socket      loaded failed failed Userspace Out-Of-Memory (OOM) Killer Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
2 loaded units listed.

[cerebrate]

See above link for real underlying issue and workaround.

[microsoft-github-policy-service]

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!