Droidspaces
Droidspaces v5.5.0 has been released! What is Droidspaces in the first place? 👀 Droidspaces is a lightweight, portable Linux containerization tool that lets you run full Linux environments on top of Android or Linux, with complete init system support including…
Droidspaces-universal-v5.5.0-2026-03-09.apk
12.7 MB
Mirrored the latest releases just in case :D
❤🔥2❤1💩1
Run real Linux on Android natively with Droidspaces
As you can see, I converted my Galaxy S10 5G into a portable home server with its own isolated network stack.
Using an Ubuntu 24.04 LTS container in Droidspaces, I set up Jellyfin, Samba, Tailscale, OpenSSH Server, and Fail2Ban in one go - no trial and error.
This is essentially a 1:1 replacement for the whacky Docker/LXC setups on Android. It just works and runs natively with zero overhead.
Droidspaces containers are fully isolated from Android. They can’t detect that they are running on an Android device and cannot see Android processes, mounts, network interfaces, or other devices on your local network - making it a secure environment for running services. This is not chroot or proot.
I access the container through Tailscale. Only ports 445 and 8096 are forwarded, allowing access to the Samba share and Jellyfin server from other devices on my home network via
Project: https://github.com/ravindu644/Droidspaces-OSS
As you can see, I converted my Galaxy S10 5G into a portable home server with its own isolated network stack.
Using an Ubuntu 24.04 LTS container in Droidspaces, I set up Jellyfin, Samba, Tailscale, OpenSSH Server, and Fail2Ban in one go - no trial and error.
This is essentially a 1:1 replacement for the whacky Docker/LXC setups on Android. It just works and runs natively with zero overhead.
Droidspaces containers are fully isolated from Android. They can’t detect that they are running on an Android device and cannot see Android processes, mounts, network interfaces, or other devices on your local network - making it a secure environment for running services. This is not chroot or proot.
I access the container through Tailscale. Only ports 445 and 8096 are forwarded, allowing access to the Samba share and Jellyfin server from other devices on my home network via
<phone-ip>:<port>.Project: https://github.com/ravindu644/Droidspaces-OSS
🗿9👏5❤1🔥1🤩1
Droidspaces v5.6.0 has been released!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.6.0
Note: After installing this release, if you are using an old kernel like 4.14.113 (this issue is specific to this kernel version), and systemd appears to hang,
Strangely, this issue does not occur on 4.9 kernels and only manifests on 4.14.113, which affects most devices, particularly Samsung devices released between 2019 and 2020.
Previously, to fix this, all clone() and unshare() syscalls had to be blocked to prevent systemd from creating sandboxes, which resolved the deadlock and allowed systemd to boot. However, this came at the cost of losing the ability to run Docker, Podman, or LXC inside a Droidspaces container on any kernel below 5.x.
In this release, that hard-coded block has been completely removed. Users can now enable the "Deadlock Shield" only if needed, directly from the container configuration menu.
As a result, users already running an upstream kernel such as 4.14.356 can now run Docker inside Droidspaces, while affected users can still enable the Deadlock Shield manually.
Also, this release focuses on fixing critical vulnerabilities in the project related to common exploits, further hardening security, and fixing a critical security hole where a device's block devices were exposed under /sys/block, even in non `--hw-access` mode.
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.6.0
Note: After installing this release, if you are using an old kernel like 4.14.113 (this issue is specific to this kernel version), and systemd appears to hang,
systemctl commands do not work, or your phone becomes unresponsive, you are affected by the grab_super() VFS deadlock bug.Strangely, this issue does not occur on 4.9 kernels and only manifests on 4.14.113, which affects most devices, particularly Samsung devices released between 2019 and 2020.
Previously, to fix this, all clone() and unshare() syscalls had to be blocked to prevent systemd from creating sandboxes, which resolved the deadlock and allowed systemd to boot. However, this came at the cost of losing the ability to run Docker, Podman, or LXC inside a Droidspaces container on any kernel below 5.x.
In this release, that hard-coded block has been completely removed. Users can now enable the "Deadlock Shield" only if needed, directly from the container configuration menu.
As a result, users already running an upstream kernel such as 4.14.356 can now run Docker inside Droidspaces, while affected users can still enable the Deadlock Shield manually.
Also, this release focuses on fixing critical vulnerabilities in the project related to common exploits, further hardening security, and fixing a critical security hole where a device's block devices were exposed under /sys/block, even in non `--hw-access` mode.
💩1
This media is not supported in your browser
VIEW IN TELEGRAM
If you are from Reddit and wondering how my S10 Jellyfin server performs,this is how:
As you can see, I'm constantly pulling heavy FLACs from the server in real-time.
Most of the FLACs are larger than 50MB.
During this testing,the CPU stays below 20%,with idle usage around 9-10%.
Temperatures stayed the same,all below 40C.Even my room temp is ~34C rn.
So,this is a huge win for me.
This setup is very efficient for streaming my music :)
Also,Android didn't kill the server.It's up and running for 8 hours according to uptime.Also,during previous testing,it held up to 2 days until my manual reboots.
As you can see, I'm constantly pulling heavy FLACs from the server in real-time.
Most of the FLACs are larger than 50MB.
During this testing,the CPU stays below 20%,with idle usage around 9-10%.
Temperatures stayed the same,all below 40C.Even my room temp is ~34C rn.
So,this is a huge win for me.
This setup is very efficient for streaming my music :)
Also,Android didn't kill the server.It's up and running for 8 hours according to uptime.Also,during previous testing,it held up to 2 days until my manual reboots.
🔥3❤🔥2💩1
Added a guide to fix the Wi-Fi power-saving issue on Android devices, which makes the networking experience sluggish when the device’s screen is turned off:
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Troubleshooting.md#wi-fi-power-save-on-causing-sluggish-networking-on-android
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Troubleshooting.md#wi-fi-power-save-on-causing-sluggish-networking-on-android
❤1💩1
Droidspaces
Built in terminal ?🌚
Droidspaces-universal-v5.6.1-2026-03-14-final.apk
14 MB
Testing... Please report any issues if they happen related to the terminal/IPv6
❤3🔥1💩1
Droidspaces
Droidspaces-universal-v5.6.1-2026-03-14-final.apk
Since no one is dropping a single screenshot, I assume the build is stable 😅
How can I tell if this has bugs in some whacky setup? You guys need to test it.
Even if it doesn’t have any bugs, you still need to report to me
Since the project is popular now, I can’t release updates every day without testing like a madman :D
Thanks for understanding the situation :)
How can I tell if this has bugs in some whacky setup? You guys need to test it.
Even if it doesn’t have any bugs, you still need to report to me
Since the project is popular now, I can’t release updates every day without testing like a madman :D
Thanks for understanding the situation :)
👍9🔥3🗿2💩1