How guritaaa/docker-android works
docker-android packages a configurable, headless Android emulator as a Docker service. The main workflow is to run the image with KVM and exposed ports, then connect an external ADB client (and optionally scrcpy) to control the emulator; an optional mounted /data volume preserves AVD data across restarts. The README documents SDK/image customization, ADB networking, and QEMU/libvirt support. No source excerpts were provided, so relationships below rely on README statements; script responsibilities and internal call paths are not inferred.
Main entry points: Dockerfile Emulator container
Components 13
Image configuration
- Docker image
Dockerfile - Build options
Dockerfile - Android SDK
Dockerfile
Emulator runtime
- Emulator container
Dockerfile - Android emulator
Dockerfile - QEMU / KVM
Dockerfile
Remote access
- ADB server
Dockerfile - ADB port
Dockerfile - ADB client
- scrcpy client
Persistent state
- AVD data
- Mounted /data
Other components
- Docker operator
Connections 15
- Docker operator → Docker image: runs
README.md - Docker operator → Build options: customizes
README.md - Docker image → Emulator container: provides
README.md - Emulator container → Android emulator: runs
README.md - Emulator container → ADB server: runs
README.md - Android emulator → QEMU / KVM: uses
README.md - Build options → Android SDK: selects
README.md - Docker operator → Emulator container: mounts KVM
README.md - Docker operator → ADB port: publishes
README.md - ADB server → ADB port: listens on
README.md - ADB client → ADB port: connects to
README.md - scrcpy client → ADB port: uses ADB
README.md - Emulator container → AVD data: stores
README.md - Docker operator → Mounted /data: mounts
README.md - Mounted /data → AVD data: preserves
README.md