It parses logcat for lines containing a string (GoogleTest), uninstalls the app and does some analysis on the parsed lines. It then changes in to a directory (workspace/GoogleTestApp) where it builds and installs an app. The script starts a headless container, if the HOSTNAME variable is set to CI. I included a script under provisioning/ndkTests.sh which demonstrates how you may use this container in a CI environment. If you just want a shell in the container, without starting Android Studio, run './run.sh bash' to bypass starting Android Studio Additional information - continous integration So it probably does not make sense to try starting via run.sh without The default docker entrypoint tries to start android-studio. You may use a Variable like this: 'HOST_NET=1. Let the emulator run on the Hosts Display environment.

HOST_DISPLAY - Allow the container to use the Display of the host.

HOST_USB - Use the USB of the Host (useful if you want your physical device to be recognized by adb inside the container).

NO_TTY - Do not run docker with -t flag.

Run.sh has some options which you can set via Environment variables. 'docker run -i $AOSP_ARGS -v pwd/studio-data:/studio-data -privileged -group-add plugdev deadolus/android-studio' You may of course change the name of the container. So you may also run 'docker pull deadolus/android-studio'. ' directly.Īn already built version is also on Docker Hub. Just run './build.sh', or 'docker build -t deadolus/android-studio.

If you don't have a display the Emulator can run with a 'dummy' display - perfect for continous integration.

You can even start an Emulator inside it. Complete Android-Studio in a Docker container.

Android studio plugin for emulator