
This includes supporting ADB, gRPC, and WebRTC.
#Docker for mac android emulator android
The Docker image creator is responsible for creating a suitable environment for the Android emulator to run. Currently, it only supports downloading the current version of the emulator, but Google say it will eventually support the possibility of downloading older versions to enable reproducing legacy test results. The former aims to automate the emulator download step described above. Two key pieces of the the Android Emulator Container Scripts are the Android emulator download script and the Docker image generator. Once the container is running, communication with the emulator is enabled through port 5555: adb connect localhost:5555ĪDB is also used to track failures due to bugs and to diagnose their cause. This last step can be automated with the provided. Once the files are available locally, Docker can be used to build the image and run it with the proper port mapping in place, ready for a connection to be established via the Android Debug Bridge (ADB) CLI tool: docker run -e "ADBKEY=$(cat ~/.android/adbkey)" -device /dev/kvm-publish The command supporting this is emu-docker which allows developers to choose a system image and emulator version from a list and then manually download it using wget. This enables the use of an Android emulator instance running remotely within a continuous testing pipeline, says Google.ĭevelopers can easily choose which emulator version to download and create a Dockerfile to containerize it.

The Android Emulator Container Scripts are a set of Python and shell scripts meant to automate the process of running the Android emulator in a Docker container. Google has just made integrating the Android Emulator within a continuous testing pipeline easier by open sourcing the Android Emulator Container Scripts and two related tools. The Android Emulator is the main tool Android developers use to test their apps.
