budtmo/docker-android

Docker-Android is a docker image built to be used for everything related to Android. It can be used for Application development and testing (native, web and hybrid-app).

1. Emulator with different device profile and skins, such as Samsung Galaxy S6, LG Nexus 4, HTC Nexus One and more.
2. Support vnc to be able to see what happen inside docker container
3. Support log sharing feature where all logs can be accessed from web-UI
4. Ability to control emulator from outside container by using adb connect
5. Integrated with other cloud solutions, e.g. Genymotion Cloud
6. It can be used to build Android project
7. It can be used to run unit and UI-Test with different test-frameworks, e.g. Appium, Espresso, etc.
8. It support (http) MCP-Server (beta-version)
9. It support AI-Agent (beta-version) - supported local-LLM server: Ollama, VLLM

1. Docker is installed on your system.

1. If you use Ubuntu OS on your host machine, you can skip this step. For OSX and Windows OS user, you need to use Virtual Machine that support Virtualization with Ubuntu OS because the image can be run under Ubuntu OS only.

2. Your machine should support virtualization. To check if the virtualization is enabled is:

   sudo apt install cpu-checker
   kvm-ok
   

3. Run Docker-Android container

   docker run -d -p 6080:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true --device /dev/kvm --name android-container budtmo/docker-android:emulator_11.0
   

4. Open http://localhost:6080 to see inside running container.

5. To check the status of the emulator

   docker exec -it android-container cat device_status
   

The default behaviour is to destroy the emulated device on container restart. To persist data, you need to mount a volume at /home/androidusr: docker run -v data:/home/androidusr budtmo/docker-android:emulator_11.0

Credit goes to Guillaume - The Parallel Interface blog

Microsoft - Advanced settings configuration in WSL

1. Add yourself to the kvm usergroup.

   sudo usermod -a -G kvm ${USER}
   

2. Add necessary flags to /etc/wsl.conf to their respective sections.

   [boot]
   command = /bin/bash -c 'chown -v root:kvm /dev/kvm && chmod 660 /dev/kvm'
   

   Then, using PowerShell, open a notepad on notepad $env:USERPROFILE\.wslconfig. Inside, put these other flags:

   [wsl2]
   nestedVirtualization=true
   

3. Restart WSL2 via CMD prompt or Powershell

   wsl --shutdown
   

command = /bin/bash -c 'chown -v root:kvm /dev/kvm && chmod 660 /dev/kvm' sets /dev/kvm to kvm usergroup rather than the default root usergroup on WSL2 startup.

nestedVirtualization flag is only available to Windows 11.

If this setup does not work, you may have an old WSL version. In that case, ignore \.wslconfig and put everything on /etc/wsl.conf, including the [wsl2] flag.

1. Build Android project
2. UI-Test with Appium
3. Control Android emulator on host machine
4. SMS Simulation
5. Jenkins
6. Deploying on cloud (Azure, AWS, GCP)

This document contains information about configurations that can be used to enable some features, e.g. log-sharing, etc.

For you who do not have ressources to maintain the simulator or to buy machines or need different device profiles, you can give a try by using Genymotion SAAS. Docker-Android is integrated with Genymotion on different cloud services, e.g. Genymotion SAAS, AWS, GCP, Alibaba Cloud. Please follow this document for more detail.

The Emulator skins are taken from Android Studio IDE and Samsung Developer Website

Due to high requests for help and to be able to actively maintain the projects, the creator has decided to create docker-android-pro. Docker-Android-Pro is a sponsor based project which mean that the docker image of pro-version can be pulled only by active sponsor.

The differences between normal version and pro version are:

List pro-version images:

This document contains detail information about how to use docker-android-pro.

See License