Windows WSL Debian Bookworm script execution

[al-sabr]

Details:

• Date | 2024-11-02 09:20:10
• Program name | DietPi-Installer
• Command | systemctl disable --now dietpi-cloudshell.service
• Exit code | 1
• DietPi version | v9.8.0 (MichaIng/master)
• Distro version | bookworm (ID=7,RASPBIAN=0)
• Kernel version | Linux Bismillah-Ar-Rahman-Ar-Rahim 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 GNU/Linux
• Architecture | amd64
• Hardware model | (ID=)
• Power supply | (EG: RAVPower 5V 1A)
• SD card | (EG: SanDisk Ultra 16 GB)

Steps to reproduce:

1. Installed Debian WSL on Windows 10
2. Tried that script https://dietpi.com/docs/hardware/#make-your-own-distribution

Expected behaviour:

• Normal script running and cleaning the OS for a DietPi initial setup.

Actual behaviour:

• Error screenshot

Extra details:

• ...

Additional logs:

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

[Joulinar]

you can have a look into https://dietpi.com/forum/t/wsl2-support-update/16276

[al-sabr]

Here a screenshot of the new status

Trying the script again and it does the same error

[Joulinar]

Did you activate systemd on WSL before? Probably a reboot is needed

[al-sabr]

Here is the tutorial : https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950

It is working ... Am I correct to have seleted Virtual Machine setup since it is running in Windows WSL 2?

[MichaIng]

Jep, VM is correct.

[al-sabr]

Jep, VM is correct.

Here is the first error I get when trying to run the first time

[Joulinar]

Yes, Installer is working with user root only

[al-sabr]

Yes, Installer is working with user root only

How do I run it then ?

[MichaIng]

That is after reboot after installer went through, right? There was no login prompt where you could login as root?

[al-sabr]

That is after reboot after installer went through, right? There was no login prompt where you could login as root?

Yes it is the first boot after install of script finished. But it is Debian WSL2 on Windows 10

[MichaIng]

And there was no login prompt where you could login as root user? Ah I see now the scrambled output on the WSL console. Does it work to connect via SSH (the IP address at least is still visible on the console).

I'll do a test installation, when I find time.

[al-sabr]

And there was no login prompt where you could login as root user? Ah I see now the scrambled output on the WSL console. Does it work to connect via SSH (the IP address at least is still visible on the console).

I'll do a test installation, when I find time.

Find time : D

[MichaIng]

I just tested it. Interestingly, on a current Windows 11 instance, WSL2 seems to setup with systemd automatically. I did:

wsl --install -d debian

Then rebooted the system, then started Debian from the start menu. It showed some "Installing ..." dialogue, which did not disappear until I closed the console and started it from the start menu again. But on that system, I only needed to install curl via APT, and could run our dietpi-installer right away. It showed some warning that the root filesystem is not located on a partition, but the naked drive, which is true:

/dev/sdc       1055762868    729944 1001329452   1% /

But one can ignore it, and it just works. Reboot, and did login automatically as root, same as in your case. As you can see, I also have no graphical issues with the console 🤔.

[al-sabr]

I just tested it. Interestingly, on a current Windows 11 instance, WSL2 seems to setup with systemd automatically. I did:

Try with Windows 10 in a VM with WSL

[MichaIng]

Sorry for the late reply. I currently do not have the time to dig out my Windows 10 laptop.

Can you try to switch the default user like that:

debian config --default-user root

This can be run from the cmd in the Windows host. Maybe it indirectly solves the weird output already.