English | 简体中文

Droidspaces

Droidspaces runs full Linux distributions as containers on a rooted Android phone or a Linux PC. Each container boots its own init system, whether systemd, OpenRC or any other, on the host's kernel.

There is no emulation and no virtual machine, so programs run at native speed. One static binary under 400 KB does all of it, and the Android app drives that binary so you never need a terminal to get started.

What you get

• A real Linux system, not a chroot, not a virtual machine. Ubuntu, Debian, Fedora, Arch, Alpine, NixOS, OpenWrt and more boot with their own init as PID 1. Services, timers, reboot from inside the container, all of it works.
• Networking that works out of the box. NAT mode gives every container its own address and internet, with no setup. Gateway mode hands a container's LAN to an OpenWrt container that does DHCP, DNS and firewalling. Macvlan puts a container straight on a wired LAN with its own address from your router.
• A desktop on your phone. Anland or Termux:X11 for the display, VirGL or Qualcomm's Turnip for the GPU, and PulseAudio for sound, all started for you. Turn on the toggles, start the container, and the desktop environment appears with sound.
• Hardware when you want it. GPU, USB, sensors and block devices can be exposed to a container with one toggle. Docker and Podman run inside containers on every supported kernel.
• Containers that stay up. On Android a container can start at boot, before you unlock the phone, and keeps running for months, whether the app is open, closed or uninstalled. Everything lives in /data/local/Droidspaces.
• The same binary on Linux. Every feature of the CLI works the same on a Linux PC. Packages are built for aarch64, armhf, x86_64, x86 and riscv64.

Requirements

Android

• A rooted device. KernelSU is recommended. Magisk and APatch work too.
• A kernel built with the options Droidspaces needs. Most stock kernels lack them. See the kernel configuration guide, or pick a phone from the community-supported devices list, which links to ready-made kernels.
• Kernel 3.10 or newer. 4.9 and newer is where most distributions work well.

Linux

• Kernel 3.10 or newer and root. Any current desktop distribution has everything else. Run sudo ./droidspaces check to confirm.

Get started

Android

1. Install the APK from the latest release, grant root, open it, and let it install the backend. Reboot when it asks.
2. Open the Containers tab, tap +, then Repository. Pick a distribution, tap Download, then Install, and walk through the setup.
3. Tap Start. Open the Panel tab and tap Terminal to get a shell.

The Android installation guide covers each step in detail.

Linux

The Linux installation guide shows how to install Droidspaces, where to get a rootfs and how to put it in an image file.

Screenshots

Home

Containers

Panel

Security

[!WARNING]

Droidspaces is a privileged container runtime.

Root inside a container is powerful, and a hostile root process can reach the host.

Do not run code you do not trust in a container, and use a normal user with sudo for daily work, as you would on any Linux machine.

Hardware access and privileged mode relax the remaining barriers further, so turn them on only when you need them.

Documentation

Everything below is also on the documentation site, rendered and searchable.

Community and contributing

Questions and help: the Telegram channel. Bugs and feature requests: GitHub issues.

Code contributions start with CONTRIBUTING.md. App translations are on Weblate:

Credits

• LXC, the architectural inspiration.
• BusyBox, the static binary the app uses for extraction and setup (our build).
• ReTerminal, Termux and LXC-Manager, the terminal emulator backend.
• JetBrains Mono, the monospace typeface in the app, under the SIL Open Font License 1.1.

License

GNU General Public License v3.0. Copyright (C) 2026 ravindu644 and contributors.