Skip to content

A rootless Android app that boots Alpine Linux: run containers (Podman/Docker/LXC) and GUI desktop apps.

docs(site): refresh landing page for 1.1.7

ExTv9fc7e2aae778
diff --git a/docs/index.html b/docs/index.html
index ee45924..0063167 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -3,9 +3,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>Podroid — Linux containers on Android, no root required</title>
- <meta name="description" content="Podroid runs rootless Podman containers on Android — full Alpine Linux VM via QEMU with a custom 6.6 kernel. No root, no custom recovery, any ARM64 device." />
- <meta property="og:title" content="Podroid — Linux containers on Android, no root required" />
+ <title>Podroid: Linux containers on Android, no root required</title>
+ <meta name="description" content="Podroid runs Podman, Docker, and LXC on Android in a real Alpine Linux VM via QEMU with a custom Linux 6.6 kernel. No root, no custom recovery, any ARM64 device." />
+ <meta property="og:title" content="Podroid: Linux containers on Android, no root required" />
<meta property="og:description" content="Spin up a real Alpine Linux VM with a full Podman runtime on any Android 9+ ARM64 device. No root, no Magisk, no AVF requirement." />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://extv.github.io/Podroid/" />
@@ -551,7 +551,7 @@
<h1>Linux containers on Android.<br /><em>No root required.</em></h1>
<p class="hero-sub">
Podroid spins up a real Alpine Linux VM using QEMU and a custom&nbsp;kernel.<br />
- You get a full Podman container runtime and a polished terminal.<br />
+ Run <strong>Podman</strong>, <strong>Docker</strong>, and <strong>LXC</strong> with a polished built-in terminal.<br />
Install the APK, tap Start, run containers.
</p>
<div class="hero-actions">
@@ -580,16 +580,16 @@
<div class="feature-icon">
<svg width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.8" viewBox="0 0 24 24"><rect x="2" y="7" width="20" height="14" rx="2"/><path d="M16 7V5a2 2 0 0 0-2-2h-4a2 2 0 0 0-2 2v2"/><line x1="12" y1="12" x2="12" y2="16"/><line x1="10" y1="14" x2="14" y2="14"/></svg>
</div>
- <h3>Rootless Podman</h3>
- <p>Full Docker-compatible container runtime. Pull from Docker Hub, run images, manage networks — all without root or custom kernel modules on the host.</p>
+ <h3>Podman, Docker, LXC</h3>
+ <p>All three major container engines work zero-config. Native kernel <code>overlay2</code> for Docker, <code>fuse-overlayfs</code> for rootless Podman, and a pre-configured <code>lxcbr0</code> bridge for LXC. Pull any OCI image and run it.</p>
</div>
<div class="feature-card">
<div class="feature-icon">
<svg width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.8" viewBox="0 0 24 24"><circle cx="12" cy="12" r="3"/><path d="M12 1v4M12 19v4M4.22 4.22l2.83 2.83M16.95 16.95l2.83 2.83M1 12h4M19 12h4M4.22 19.78l2.83-2.83M16.95 7.05l2.83-2.83"/></svg>
</div>
- <h3>Custom Linux 6.6 Kernel</h3>
- <p>Compiled from scratch with netfilter, bridge, overlayfs, veth, and cgroup v2 built-in. Every feature Podman needs is already there — no module loading.</p>
+ <h3>Custom Linux 6.6.87 Kernel</h3>
+ <p>Compiled from scratch with netfilter, bridge, overlayfs, veth, IPVS, VXLAN, IPsec, and cgroup v2 all built-in. Docker's <code>check-config.sh</code> reports zero fixable complaints.</p>
</div>
<div class="feature-card">
@@ -633,7 +633,7 @@
<div class="container">
<p class="section-label">Comparison</p>
<h2>How Podroid stacks up</h2>
- <p class="section-sub">Termux gives you a Linux shell. Google Terminal gives you a VM with optional manual container setup. Podroid ships a full container runtime out of the box.</p>
+ <p class="section-sub">Termux gives you a Linux shell. Google Terminal gives you a VM with optional manual container setup. Podroid ships three container engines out of the box.</p>
<div class="table-wrap">
<table>
@@ -669,7 +669,7 @@
</tr>
<tr>
<td class="row-label">Real container runtime</td>
- <td class="col-podroid"><span class="check">✓ Podman</span></td>
+ <td class="col-podroid"><span class="check">✓ Podman + Docker + LXC</span></td>
<td><span class="cross">✗</span></td>
<td><span class="partial">manual setup</span></td>
</tr>
@@ -738,7 +738,7 @@
<div class="container">
<p class="section-label">Architecture</p>
<h2>How it works</h2>
- <p class="section-sub">Three channels, one VM, zero root. Here's what happens when you tap Start.</p>
+ <p class="section-sub">Four sockets, one VM, zero root. Here's what happens when you tap Start.</p>
<div class="arch-diagram"><span class="arch-white">┌────────────────────── Android App (Compose) ─────────────────────────┐
│ │
@@ -750,11 +750,16 @@
│ │ │
│ ┌─────────────────▼────────────────┐ │
│ │ Alpine Linux 3.23 VM │ │
+ │ │ /sbin/init (busybox) │ │
+ │ │ OpenRC (PID 1) │ │
│ │ ┌──────────┐ ┌──────────────┐ │ │
- │ │ │ Podman │ │ Linux 6.6 │ │ │
- └──►│ │(rootless)│ │ (custom) │ │◄───┘
- boot stages │ └──────────┘ └──────────────┘ │ libpodroid-bridge.so
- │ │ PTY ↔ virtio-console
+ │ │ │ Podman + │ │ Linux 6.6 │ │ │
+ └──►│ │ Docker │ │ (custom) │ │◄───┘
+ boot stages │ │ + LXC │ └──────────────┘ │ libpodroid-bridge.so
+ │ └──────────┘ │ PTY ↔ virtio-console
+ │ │
+ │ /dev/vda ext4 overlay (rw) │
+ │ /dev/vdb squashfs base (ro) │
└──────────────────────────────────┘</span>
<span class="arch-green">terminal.sock</span> ↔ hvc0 → primary shell I/O
@@ -767,21 +772,21 @@ qmp.sock → runtime port-forward control</div>
<div class="step-num">1</div>
<div class="step-body">
<h4>QEMU loads the kernel</h4>
- <p>Custom Linux 6.6.87 + initramfs extracted from APK assets on first launch.</p>
+ <p>Custom Linux 6.6.87 + a tiny initramfs and a 41 MB Alpine squashfs are extracted from APK assets on first launch.</p>
</div>
</div>
<div class="step">
<div class="step-num">2</div>
<div class="step-body">
- <h4>Phase 1: storage mount</h4>
- <p>Init mounts <code>storage.img</code> as overlayfs for persistent container data.</p>
+ <h4>Overlay + switch_root</h4>
+ <p>Init mounts the squashfs as the read-only base, the ext4 image as the writable upper, then <code>switch_root</code>s into <code>/sbin/init</code>.</p>
</div>
</div>
<div class="step">
<div class="step-num">3</div>
<div class="step-body">
- <h4>Phase 2: services start</h4>
- <p>Networking (SLIRP + MASQUERADE), cgroup v2, Podman runtime, and Dropbear SSH come up.</p>
+ <h4>OpenRC services start</h4>
+ <p>Cgroup v2, network, Docker bind-mount, <code>lxcbr0</code> bridge, MASQUERADE NAT, sysctls, and Dropbear SSH all come up automatically.</p>
</div>
</div>
<div class="step">
@@ -814,7 +819,7 @@ qmp.sock → runtime port-forward control</div>
</div>
<div class="qs-step">
<div class="qs-step-num">3</div>
- <p><strong>Tap Start VM.</strong> Watch the boot progress — typically ready in 6–15 seconds.</p>
+ <p><strong>Tap Start VM.</strong> Watch the boot progress; typically ready in 6–15 seconds.</p>
</div>
<div class="qs-step">
<div class="qs-step-num">4</div>
@@ -826,17 +831,16 @@ qmp.sock → runtime port-forward control</div>
</div>
</div>
- <div class="code-block"><span class="c-comment"># hello world</span>
+ <div class="code-block"><span class="c-comment"># Podman: works out of the box</span>
<span class="c-prompt"># </span><span class="c-cmd">podman run --rm alpine echo hello</span>
-<span class="c-comment"># interactive shell</span>
-<span class="c-prompt"># </span><span class="c-cmd">podman run --rm -it ubuntu bash</span>
+<span class="c-comment"># Docker: install + start, then go</span>
+<span class="c-prompt"># </span><span class="c-cmd">apk add docker &amp;&amp; rc-service docker start</span>
+<span class="c-prompt"># </span><span class="c-cmd">docker run -d -p 8080:80 nginx</span>
-<span class="c-comment"># nginx on port 8080</span>
-<span class="c-prompt"># </span><span class="c-cmd">podman run -d -p 8080:80 nginx</span>
-
-<span class="c-comment"># list running containers</span>
-<span class="c-prompt"># </span><span class="c-cmd">podman ps -a</span>
+<span class="c-comment"># LXC: bridge + MASQUERADE pre-configured</span>
+<span class="c-prompt"># </span><span class="c-cmd">apk add lxc lxc-templates</span>
+<span class="c-prompt"># </span><span class="c-cmd">lxc-create -t busybox -n test &amp;&amp; lxc-start -n test</span>
<span class="c-comment"># SSH in from your laptop</span>
<span class="c-prompt">$ </span><span class="c-cmd">ssh root@&lt;phone-ip&gt; -p 9922</span></div>
@@ -863,21 +867,21 @@ qmp.sock → runtime port-forward control</div>
<details>
<summary>Why not just use Termux + proot?</summary>
<div class="faq-answer">
- Termux is great for a Linux shell, but it runs on Android's host kernel. That kernel doesn't have the namespaces, cgroups, or netfilter rules needed for real containers. <code>proot</code> is a chroot emulation — containers built for Docker/Podman won't work reliably. Podroid runs a real VM with its own kernel purpose-built for Podman, so every OCI image from Docker Hub just works.
+ Termux is great for a Linux shell, but it runs on Android's host kernel. That kernel doesn't have the namespaces, cgroups, or netfilter rules needed for real containers. <code>proot</code> is a chroot emulation; containers built for Docker, Podman, or LXC won't work reliably. Podroid runs a real VM with its own custom kernel, so every OCI image from Docker Hub just works.
</div>
</details>
<details>
<summary>How is this different from Google Terminal / AVF?</summary>
<div class="faq-answer">
- Google's Terminal app uses Android Virtualization Framework (AVF) — a system-level hypervisor available on recent Pixel devices. It gives you a Debian VM but no container runtime and limited configurability. Podroid uses QEMU TCG (software emulation), which means it works on <em>any</em> ARM64 Android 9+ device — not just Pixels — and ships with a full Podman runtime, port forwarding, SSH, and a configurable terminal.
+ Google's Terminal app uses Android Virtualization Framework (AVF), a system-level hypervisor available only on recent Pixel devices. It gives you a Debian VM but no container runtime and limited configurability. Podroid uses QEMU TCG (software emulation), so it works on <em>any</em> ARM64 Android 9+ device, not just Pixels, and ships with three container engines, port forwarding, SSH, and a configurable terminal.
</div>
</details>
<details>
<summary>Is performance usable? QEMU is slow.</summary>
<div class="faq-answer">
- TCG is software emulation, so compute-heavy workloads are slower than native. However, Podroid ships several optimizations: a 256–512 MB translation cache, a dedicated I/O thread for virtio-blk (big win for image pulls), ZRAM swap for 2× effective RAM, and <code>mitigations=off</code> in the guest kernel for a 5–15% CPU gain. For typical dev tasks — running a web server, a database, CLI tools — it's very usable.
+ TCG is software emulation, so compute-heavy workloads are slower than native. Podroid ships several optimizations: a 256–512 MB translation cache, a dedicated I/O thread for virtio-blk (big win for image pulls), ZRAM swap for 2× effective RAM, and <code>mitigations=off</code> in the guest kernel for a 5–15% CPU gain. For typical dev tasks like running a web server, a database, or CLI tools, it's very usable.
</div>
</details>
@@ -891,14 +895,14 @@ qmp.sock → runtime port-forward control</div>
<details>
<summary>How much storage does it use?</summary>
<div class="faq-answer">
- The APK is ~200 MB (QEMU + kernel + initramfs + fonts). On first launch you choose a VM disk size between 2 GB and 64 GB — this is a sparse <code>storage.img</code> that only grows as you pull images and install packages.
+ The APK is ~200 MB (QEMU + kernel + initramfs + Alpine squashfs + fonts). On first launch you choose a VM disk size between 2 GB and 64 GB; this is a sparse <code>storage.img</code> that only grows as you pull images and install packages.
</div>
</details>
<details>
<summary>Can I connect from my laptop over SSH?</summary>
<div class="faq-answer">
- Yes. Dropbear SSH runs on port 9922 by default (configurable in Settings). As long as your laptop and phone are on the same network, <code>ssh root@&lt;phone-ip&gt; -p 9922</code> gives you a remote shell — useful for VS Code Remote or any SSH client.
+ Yes. Dropbear SSH runs on port 9922 by default (configurable in Settings). As long as your laptop and phone are on the same network, <code>ssh root@&lt;phone-ip&gt; -p 9922</code> gives you a remote shell. Useful for VS Code Remote or any SSH client.
</div>
</details>