WSL2 Deployment Guide

WSL2 Deployment Guide

Running Android-in-Docker under Windows Subsystem for Linux (WSL2) requires additional kernel modules that are typically omitted from Microsoft's stock WSL kernel.

---

Kernel Requirements

Redroid relies on Android Binder drivers. If you use Microsoft's default kernel, container startup will fail with Binder device errors.

Compiling or Loading the Damru WSL Kernel

Damru provides a custom WSL2 kernel with Binder, bridge-NAT, and iptables modules enabled.

1. Download our pre-compiled kernel from the repository releases.
2. Place the kernel in your Windows user directory (e.g. C:\Users\<Name>\vmlinux).
3. Create or update your C:\Users\<Name>\.wslconfig file:

[wsl2]
kernel=C:\\Users\\<Name>\\vmlinux

4. Restart WSL in PowerShell:

wsl --shutdown

---

WSL Networking & Bridging

Windows and WSL share network interfaces. To prevent network corruption:

• Damru routes WSL Redroid instances using Docker Bridge Networking on custom ADB ports (e.g., 5600, 5601).
• If DNS resolution breaks in your containers, execute:

  python -m damru fix-internet

  This command inserts MASQUERADE rules into your local iptables, allowing the container bridge (docker0) to forward packets correctly.