If Droidspaces doesn't work for you, it falls into two categories.

01. Your kernel version

- If you have a legacy kernel, probably 4.19 or older, you fall into this category.

- As I clearly stated in multiple places in my README, you cannot run modern systemd like v258 on these kernels. They fail to boot, every systemctl command hangs, and everything will be broken. Even LXC cannot boot them. There is no fix for this.

If you wonder why, modern systemd requires modern syscalls, which older kernels often lack. So, if you run foreground mode with the -f flag, you will see thousands of "function not implemented" errors.

What to try on these kernels?

You can try anything below systemd v258, or any distro with a different init system like OpenRC, runit, s6, etc.

My picks: Ubuntu 20.04, 22.04, 24.04, 25.04, 25.10; Alpine 3.23; Gentoo OpenRC flavor.

Notes: Especially in Kernel 4.14.113, which the Galaxy S10 uses by default, you cannot boot any systemd-based distros without enabling the "Deadlock Shield". This is a kernel bug that causes the entire systemd and host to become unresponsive when booting a container.

Symptoms: Systemd hangs, even in older distros. The entire host becomes unresponsive. You cannot reboot or power off your device.

Solution: Either enable Deadlock Shield or use an upstreamed kernel like 4.14.356.

02. Your rooting solution

- As I clearly stated in the official documentation, Droidspaces on Magisk or Apatch is highly unstable. You will face weird issues with these solutions.

More info:
https://github.com/ravindu644/Droidspaces-OSS/issues/11#issuecomment-4036688816

Droidspaces requires a custom kernel anyway. Why can't anyone switch to KernelSU when compiling their kernels?