An optimized docker image includes Android, Kotlin, Flutter sdk.
It includes the following components:
The docker image is publicly automated build on Docker Hub based on the Dockerfile in this repo, so there is no hidden stuff in it. To pull the latest docker image:
docker pull mingc/android-build-box:latest
Hint: You can use a tag to a specific stable version,
rather than latest of docker image, to avoid breaking your build.
e.g. mingc/android-build-box:1.19.0.
Checkout Tags (bottom of this page) to see all the available tags.
You can use this docker image to build your Android project with a single docker command:
cd <android project directory> # change working directory to your project root directory.
docker run --rm -v `pwd`:/project mingc/android-build-box bash -c 'cd /project; ./gradlew build'
Run docker image with interactive bash shell:
docker run -v `pwd`:/project -it mingc/android-build-box bash
If you have an Android project in a Bitbucket repository and want to use the pipeline feature to build it,
you can simply specify this docker image.
Here is an example of bitbucket-pipelines.yml:
image: mingc/android-build-box:latest
pipelines:
default:
- step:
caches:
- gradle
- gradle-wrapper
- android-emulator
script:
- bash ./gradlew assemble
definitions:
caches:
gradle-wrapper: ~/.gradle/wrapper
android-emulator: $ANDROID_HOME/system-images/android-21
The caches are used to store downloaded dependencies from previous builds, to speed up the next builds.
Here is an example .github/workflows/main.yml to build a Flutter project with this docker image:
name: CI
on: [push]
jobs:
build:
runs-on: ubuntu-18.04
container: mingc/android-build-box:latest
steps:
- uses: actions/checkout@v2
- uses: actions/cache@v1
with:
path: /root/.gradle/caches
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }}
restore-keys: |
${{ runner.os }}-gradle-
- name: Build
run: |
echo "Work dir: $(pwd)"
echo "User: $(whoami)"
flutter --version
flutter analyze
flutter build apk
- name: Archive apk
uses: actions/upload-artifact@v1
with:
name: apk
path: build/app/outputs/apk
- name: Test
run: flutter test
- name: Clean build to avoid action/cache error
run: rm -fr build
Using guidelines from...
...You can write a script to create and launch an ARM emulator, which can be used for running integration tests or instrumentation tests or unit tests:
#!/bin/bash
# Download an ARM system image to create an ARM emulator.
sdkmanager "system-images;android-16;default;armeabi-v7a"
# Create an ARM AVD emulator, with a 100 MB SD card storage space. Echo "no"
# because it will ask if you want to use a custom hardware profile, and you don't.
# https://medium.com/@AndreSand/android-emulator-on-docker-container-f20c49b129ef
echo "no" | avdmanager create avd \
-n Android_4.1_API_16 \
-k "system-images;android-16;default;armeabi-v7a" \
-c 100M \
--force
# Launch the emulator in the background
$ANDROID_HOME/emulator/emulator -avd Android_4.1_API_16 -no-skin -no-audio -no-window -no-boot-anim -gpu off &
# Note: You will have to add a suitable time delay, to wait for the emulator to launch.
Note that x86_64 emulators are not currently supported. See Issue #18 for details.
If you want to build the docker image by yourself, you can use following command. The image itself is around 5 GB, so check your free disk space before building it.
docker build -t android-build-box .
You can use a tag to a specific stable version, rather than latest of docker image,
to avoid breaking your build. For example mingc/android-build-box:1.19.0
Note: versions 1.0.0 up to 1.17.0 included every single Build Tool version and every
Android Platform version available. This generated large Docker images, around 5 GB.
Newer versions of android-build-box only include a subset of the newest Android Tools,
so the Docker images are smaller.
If you want to enhance this docker image or fix something, feel free to send pull request.
Content type
Image
Digest
Size
4.3 GB
Last updated
almost 6 years ago
docker pull ccfiel/android-build-box