Systemd services failing on WSL2

[zoltan-magyar]

Describe the issue After a fresh installation on WSL version 1.0.3.0, the following services fail, other services seem to be fine:

• systemd-sysctl.service
• systemd-sysusers.service
• systemd-tmpfiles-setup-dev.service
• systemd-tmpfiles-setup.service

All of them with the following error: (code=exited, status=243/CREDENTIALS)

To Reproduce Fresh installation of ArchWSL, as per documentation:

• set up root password
• create default user
• initialize keyring

wsl.conf contents (default):

[boot]
systemd=true

[automount]
enabled = true
options = "metadata"
mountFsTab = true

Expected behavior The systemd related services should start without problem.

Enviroment:

• Windows build number: 10.0.22621.1194
• WSL version 1/2: WSL2 (version: 1.0.3.0)
• ArchWSL version: 22.10.16.0
• ArchWSL Installer type: appx
• Launcher version: 22020900

[zoltan-magyar]

This problem is related to WSL itself:

/microsoft/WSL/issues/8879

[MorphBonehunter]

Hey @zoltan-magyar, you are right, that's a problem with wsl. But the issue you mentioned isn't related to that. The cause of the problem is described in https://github.com/microsoft/WSL/issues/8996#issuecomment-1295953046 and was fixed in wsl 1.1.0 (pre release). In the meantime version 1.1.3 is latest and should be available to download soon (if you update from ms store).