systemd-firstboot.service prevents system from booting up

[ZeroAurora]

Update

dbus.socket is actually being blocked by another service systemd-firstboot. This service stuck on boot and prevents the system from fully booting up. The following original issue is only for referencing.

No journals, no warnings or errors. I can't really find out what's wrong.

I tried to upgrade the system, terminate WSL and "reboot" it but it's of no use. The only way to get it "up and running" magically is to start a Debian (or any other distros that can run DBus/systemd) WSL instance by side with DBus running.

And the magic persists, even if I do wsl --shutdown.

This should be a half upstream problem but I can't determine where is wrong. Posting here for help.
uname -a: Linux ZA-Desktop 5.15.137.3-microsoft-standard-WSL2 #1 SMP Mon Nov 6 23:32:38 UTC 2023 x86_64 GNU/Linux
wsl --version:

WSL 版本： 2.1.0.0
内核版本： 5.15.137.3-1
WSLg 版本： 1.0.59
MSRDC 版本： 1.2.4677
Direct3D 版本： 1.611.1-81528511
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22635.2552

Cause

systemd-firstboot.service sticks on first boot, thus blocking other services from booting up.

I tried to use other distros and they just works, without firstboot sticking.

[ZeroAurora]

Noticed that actually the system isn't fully booted up. This is the cause for dbus not starting.
Some dev suggested to disable sshd service, but not working for my env.
I discovered that the boot process stuck at systemd-firstboot.service by running sudo systemctl list-jobs.
Killed it and works.
Changing the issue title...

[ZeroAurora]

After discovering with that dev, we finally found the cause: /etc/machine-id is mounted RO by WSL.
Last question: why? why not others?

[ZeroAurora]

Transferring this issue to bootstrap repo...

[Fearyncess]

https://github.com/AOSC-Dev/aoscbootstrap/blob/master/assets/cleanup.sh#L43 this line makes /etc/machine-id missing in generated tarball. thus let wsl or the other things hijacked this file, let it become a read-only file.

there is a temporary solution: create a empty file in the tarball.