Install on Linux

Native host networking

On Linux network_mode: host works out of the box — nothing to toggle (unlike Docker Desktop on macOS / Windows). The bot container shares the host loopback, so it reaches adb at 127.0.0.1:5037 directly.

1. Install Docker Engine + ADB

You need Docker Engine with the Compose v2 plugin, plus adb on your PATH. Pick your distro:

Debian / Ubuntu

# Docker Engine + Compose plugin (official convenience script)
curl -fsSL https://get.docker.com | sudo sh

# Android platform tools (adb)
sudo apt update && sudo apt install -y android-tools-adb

Fedora

sudo dnf -y install dnf-plugins-core
sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo
sudo dnf -y install docker-ce docker-ce-cli containerd.io docker-compose-plugin

sudo systemctl enable --now docker
sudo dnf -y install android-tools

Arch

sudo pacman -S --needed docker docker-compose android-tools
sudo systemctl enable --now docker

Verify both are ready:

docker compose version   # Compose v2.x
adb version

Run Docker without sudo

Add yourself to the docker group so you don’t need sudo for every command — then log out and back in (or run newgrp docker) for it to take effect:

sudo usermod -aG docker "$USER"

Optional: emulator choices

BlueStacks is the known-good default, but Linux can also run Autopilot against any Android target that shows up in adb devices and can be kept at 720 × 1280 portrait, 320 DPI, English game language.

Option	When to use it	Setup notes
Android Studio Emulator	You want the official Android emulator and already have Android Studio / SDK tools installed.	Create a phone AVD with a custom 720 × 1280 portrait hardware profile, set density to 320 DPI, launch it, then confirm adb devices shows an emulator-#### serial.
Waydroid	You want a lightweight Linux-native Android container on a Wayland desktop.	Install and initialize Waydroid for your distro, start the session, connect ADB with adb connect <waydroid-ip>:5555, then verify it appears in adb devices. Waydroid is optional/advanced; test one account first before scaling.

2. Run the stack

1. Fetch the compose file

   curl -fsSL https://batazor.github.io/autopilot-page/docker-compose.prod.yml -o docker-compose.prod.yml

2. Start ADB and confirm your emulator is visible

   adb start-server
   adb devices        # your emulator/device should be listed as "device"

3. Verify the display profile — must be 720 × 1280 @ 320 DPI:

   adb shell wm size
   adb shell wm density

   Also open the game once and set its language to English. See Emulator setup for the full list.

4. Pull and start redis + bot + api + web:

   docker compose -f docker-compose.prod.yml up -d --pull always

5. Open the dashboard

   xdg-open http://127.0.0.1:3000/overview

First start

The bot service starts automatically — no activation step is needed. Open the dashboard and you’re ready to add a device and your accounts.

Troubleshooting

adb devices is empty inside the container

If adb devices works on the host but the bot can’t see the emulator, the host’s adb server may be bound somewhere the container can’t reach. Restart it and re-check, then confirm the bot container shares the host network:

adb kill-server && adb start-server
docker compose -f docker-compose.prod.yml exec bot adb devices

See Troubleshooting for the full list of common failures.