Skip to content

Latest commit

 

History

History
70 lines (46 loc) · 2.54 KB

Readme.md

File metadata and controls

70 lines (46 loc) · 2.54 KB

Forked from https://github.com/Deadolus/android-studio-docker/

Right now you need to build it, takes 10+ minutes.

Flutter needs to be set up with flutter doctor

The build scripts creates a directory where you can put your projects.

You can attach to the container with the command from utils/docker_attach_latest.sh

I needed to run xhost +local:docker to start the Studio GUI, probably because of wayland. You need to be in the docker group.

compose.yml doesn't work yet

Android-Studio docker container

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

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

Contains flutter too.

Tested on Linux only.

Building without docker compose

Just run "./build.sh",

Running without docker compose

Run

"HOST_DISPLAY=1 ./run.sh"

run.sh has some options which you can set via Environment variables.

  • NO_TTY - Do not run docker with -t flag
  • DOCKERHOSTNAME - set Docker Hostname. I use it to run tests headless
  • HOST_USB - Use the USB of the Host (useful if you want your physical device to be recognized by adb inside the container)
  • HOST_NET - Use the network of the host
  • HOST_DISPLAY - Allow the container to use the Display of the host. E.g. Let the emulator run on the Hosts Display environment.

You may use a Variable like this: "HOST_NET=1 ./run.sh"

The default docker entrypoint tries to start android-studio. So it probably does not make sense to try starting via run.sh without HOST_DISPLAY=1. 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

I included a script under provisioning/ndkTests.sh which demonstrates how you may use this container in a CI environment. The script starts a headless container, if the HOSTNAME variable is set to CI. It then changes in to a directory (workspace/GoogleTestApp) where it builds and installs an app. It parses logcat for lines containing a string (GoogleTest), uninstalls the app and does some analysis on the parsed lines. While this script probably does not make much sense FOR YOU, it might be useful as a guiding point for you.

Contributors

@Deadolus
@guilhermelinhares
@mtomcanyi
@Naveenkhegde
@BenBlumer