Android meets Docker
summary
Provides a ready Docker image for Android CI that mounts the Android SDK as an external volume to avoid auFS update failures and to let teams share and update SDKs independently, with benchmarks: a simple build 40s on bare metal, container + host SDK adds <1s, NFS adds ~2s; a full CI run is ~6 minutes on an on‑prem cached node versus ~10+ minutes on cloud CI. Notes emulator tradeoffs (x86 emulator ~20s vs ARM >2 minutes), image sizes (base 563 MB, VNC +60 MB), JVM fixes (add container-aware Java options; exit 137 = OOM/kernel kill), and recommends Gradle mirrors and dependency caching.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:41Developer Story
- 2:40Pain in the Admin
- 3:14Containerization vs Virtualization
- 4:39Why Docker?
- 7:46Where the problem comes
- 10:54Dockerille Best Practices
- 12:50Different Approaches
- 14:06Solution for SDK update
- 17:04Benchmark
- 18:39Performance Comparison
- 20:09Android Devices
- 24:03VNC
- 24:46Performance of
- 25:51Out Of Memory
- 26:45Memory Matters
- 31:07Can we get any better?
- 31:50Gradie distrutons mirror server
- 32:42And better?
- 33:23Reveal machine-dependent problem
- 34:45What else for mobile
related talks
11mRunning Android emulators in Travis CI
32mAndroid on Docker Containers in a Nutshell
24mAndroid CI in the cloud (en)
34mRun your Appium tests using Docker-Android
51mEmbedded Android #2 - Working with the AOSP
38mTest Inside Containers: Dockerize Appium Tests
29mBuilding CI pipeline based on TeamCity & Docker in Android Team
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem