https://github.com/ravindu644/Droidspaces-OSS/compare/v6.1.5...v6.2.0/

Droidspaces is a lightweight, portable Linux containerization tool that lets you run full Linux environments on top of Android, with complete init system support including systemd, OpenRC, and other init systems (runit, s6, etc.). What makes Droidspaces unique is its zero-dependency, native execution on Android. It's statically compiled against musl libc. If your device runs a Linux kernel, Droidspaces runs on it. No Termux, no middlemen, no setup overhead. - Tiny footprint: under 400KB - Truly native: runs directly on Android without any dependencies - Wide architecture support: aarch64, armhf, x86_64, x86, and riscv64 as a single static binary - Beautiful Android app: manage unlimited containers and do everything the CLI can, all from a clean, intuitive GUI What is Droidspaces? Droidspaces is a container runtime that uses Linux kernel namespaces to run full Linux distributions with a real init system (systemd, OpenRC, etc.) as PID 1. Unlike traditional chroot, which simply changes the apparent root directory, Droidspaces creates proper process isolation. Each container gets its own PID tree, its own mount table, its own hostname, its own IPC resources, and its own cgroup hierarchy. The result is a full Linux environment that feels like a lightweight virtual machine, but with zero performance overhead because it shares the host kernel directly. Droidspaces is designed to work natively on Android, handling all kernel quirks, SELinux conflicts, complex networking scenarios, and encryption issues that break other container tools. The entire runtime is a single static binary under 400KB, compiled against musl libc with no external dependencies. Features - Init System Support: Run systemd, OpenRC or any other init system as PID 1. Full service management and proper boot/shutdown/reboot sequences. - Deep Android Integration: Supports two daemon modes: Native init.rc (lowest-level integration with auto-spawn/unkillable persistence) and Userspace Daemon (app-togglable, starts via post-fs-data.sh, no image modification required). Both modes bypass root-domain seccomp blocks to ensure stable container lifecycles. - Namespace Isolation: Complete isolation via PID, MNT, UTS, IPC, and Cgroup namespaces. Each container has its own process tree, mount table, hostname, IPC resources, and cgroup hierarchy. - Network Isolation: 3 networking modes (Host, NAT, None). Pure network isolation via CLONE_NEWNET (NAT/None modes) or shared host networking (Host mode). - Android GPU Acceleration: Native hardware acceleration for Qualcomm Adreno GPUs via the Turnip driver. Use pre-built rootfs templates for an out-of-the-box experience. - Port Forwarding: Forward host ports to the container in NAT mode (e.g., --port 22:22). Supports TCP and UDP, as well as ranges like 1-500:1-500. - Volatile Mode: Ephemeral containers using OverlayFS. All changes are stored in RAM and discarded on exit. Perfect for testing and development. - Custom Bind Mounts: Map host directories into containers at arbitrary mount points. Supports both chained (-B a:b -B c:d) and comma-separated (-B a:b,c:d) syntax. - Hardware Access Mode: Expose host hardware (GPU, cameras, sensors, USB, block devices) directly to your containers with a single configuration toggle. - Multiple Containers: Run unlimited containers simultaneously, each with its own name, PID file, and configuration. Start, stop, enter, and manage them independently. - In-container Reboot Support: Restart the container remotely without touching Droidspaces. - Android Storage: Bind-mount /storage/emulated/0 into the container for direct access to the device's shared storage. - PTY/Console Support: Full PTY isolation. Foreground mode provides an interactive console with proper terminal resize handling (binary only with the -f flag). - Multi-DNS Support: Configure custom DNS servers (comma-separated) to bypass the host's default DNS lookup. - SELinux Permissive Mode: Optionally set SELinux to permissive mode during container boot if needed. - Rootfs Image / Direct Block Device Support: Boot containers from ext4 .img files with automatic loop mounting, filesystem checks, and SELinux context hardening. Mounting block devices like partitions and SD cards is supported in the CLI! - Auto-Recovery: Automatic stale PID file cleanup, container scanning for orphaned processes, and robust config resurrection via in-memory metadata syncing from /run/droidspaces. - Cgroup Isolation (v1/v2): Per-container cgroup hierarchies (/sys/fs/cgroup/droidspaces/<name>) with full systemd compatibility. Supports both legacy v1 and modern v2 hierarchies. - Adaptive Security & Deadlock Shield: Kernel-aware BPF filters resolve FBE keyring conflicts automatically on legacy kernels. A manual Deadlock Shield toggle is available to fix the specific VFS grab_super() deadlock on affected legacy devices (e.g., kernel 4.14.113). - Privileged Mode: Gain full access with the --privileged flag! Use with caution. Requirements Droidspaces supports Android devices running Linux kernel 3.10 and above: - Kernel 3.10: Supported (Legacy). Minimum floor. Basic namespace support. - Kernel 4.4 - 4.19: Stable (Hardened). Full support up to modern distros with systemd older than v258. - Kernel 5.4 - 5.10: Recommended (Mainline). Full feature support including nested containers and Cgroup v2. - Kernel 5.15+: Premium (Full). Best performance and maximum compatibility with all modern distributions. Your device must be rooted. Supported rooting methods: - KernelSU: Fully Supported (Recommended) - APatch: Supported (requires Daemon Mode) - Magisk: Supported (requires Daemon Mode) Note: GrapheneOS is not supported. SuSFS is not supported. License Copyright © 2026 ravindu644 and contributors. Droidspaces is licensed under the GNU General Public License v3.0.