-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluate the possibility to run emulators through Docker #61
Comments
Just spent 5 min doing Google searches 🙈 Google POC:https://github.com/google/android-emulator-container-scripts
Exposes a web site streaming emulators but might be a good resource |
Would some like to pair-program this together ? tried with @sjcqs suggestion : https://github.com/google/android-emulator-container-scripts |
Finally succeeded creating, starting and adb-connecting to a docker-hosted emulator. 🎉 |
@AchrafAmil I'm interested to PP with you to learn how you pull that off 😅 |
Do you think the image you were able to build today could run as a service container ? We should be able to communicate to the service container with ADB. https://docs.github.com/en/actions/configuring-and-managing-workflows/about-service-containers |
it's a docker container inside another docker container. The nested android-emulator docker-container runs in parallel thanks to docker compose and exposes a tcp port to bridge with ADB. So we can indeed communicate with the nested docker container throw ADB. |
Google will provide Android images for Docker 👌 https://github.com/google/android-emulator-container-scripts |
Running Android emulator through Docker seems possible, for instance with this repo https://github.com/budtmo/docker-android.
Even if running emulator on CI is far from optimal, as solution like Firebase Test Lab are far more efficient in time and ressource, the ability to run emulator on CI might still be needed by some devs.
We should investigate the possibility and the cost of running such emulator, from our Docker image, ideally using sibling container (sharing host Docker socket).
The text was updated successfully, but these errors were encountered: