cirruslabs / docker-images-android

Android SDK Docker Images

Docker images with Android SDK

You can either use it in CI or run locally via Docker:

docker run --rm -it \
  --volume "$PWD:/build" \
  --workdir /build \
  ghcr.io/cirruslabs/android-sdk:34 \
  ./gradlew :app:assembleDebug

The example above mounts current working directory and runs a Gradle build.

GitHub Container Registry

https://github.com/cirruslabs/docker-images-android/pkgs/container/android-sdk

docker-images-android's Issues

Use of SDK 31

Hello, any advance in using SDK 31?
Thanks

No Java

The result of 'flutter doctor' indicates that no Java is in the image

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.0.0, on Microsoft Windows [version 10.0.19044.2604], locale fr-CA)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
X No Java Development Kit (JDK) found; You must have the environment variable JAVA_HOME set and the java binary in your PATH. You can download the JDK from
https://www.oracle.com/technetwork/java/javase/downloads/.
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.24)
[!] Android Studio (version 2022.1)
X Unable to find bundled Java version.
[√] VS Code (version 1.76.2)
[√] Connected device (3 available)
[√] HTTP Host Availability

Add an integration test

I'm afraid that changes like #66 might break something (e.g. the emulator), so it'd be great if there was a CI job serving as a smoke test that would start an emulator and try to build&test a simple "Hello World" Android app.

`andoid-sdk:33` built image is not using latest `tools` image

@fkorotkov
It looks like the triggered CI workflow from yesterday #54 has not correctly included the transitive dependency of tools in the android-sdk image.

Latest tools digest is sha256:2d9c9176a44b359070057829c9bd9416f1b40618748b24e732ef6fcd61017321
and the android-sdk image uploaded yesterday is using the tools with digest sha256:26895ef68b93d100a657db8eb14ca544eb17791a8bb03dfab6116bb6799004ab

Maybe it is necessary to force pull transitive images before building each image in Cirrus CI?

Probably a temporary solution would be to trigger again the CI for the android repo and then again on the Flutter repo, which conveniently enough has released a hotfix update yesterday 3.10.6

This behavior can be seen in the CI logs:

tools push step

https://cirrus-ci.com/task/4882704085286912?logs=build_tools#L3366

#7 exporting to image
#7 pushing layers 6.9s done
#7 pushing manifest for ghcr.io/cirruslabs/android-sdk:tools@sha256:2d9c9176a44b359070057829c9bd9416f1b40618748b24e732ef6fcd61017321
#7 pushing manifest for ghcr.io/cirruslabs/android-sdk:tools@sha256:2d9c9176a44b359070057829c9bd9416f1b40618748b24e732ef6fcd61017321 1.1s done
#7 DONE 45.1s

android-sdk build step

https://cirrus-ci.com/task/4882704085286912?logs=build_sdk#L0

docker buildx build --push \
  --tag ghcr.io/cirruslabs/android-sdk:33 \
  sdk/33
#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 326B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/cirrusci/android-sdk:tools
#3 DONE 0.7s
#4 [1/2] FROM docker.io/cirrusci/android-sdk:tools@sha256:26895ef68b93d100a657db8eb14ca544eb17791a8bb03dfab6116bb6799004ab
#4 resolve docker.io/cirrusci/android-sdk:tools@sha256:26895ef68b93d100a657db8eb14ca544eb17791a8bb03dfab6116bb6799004ab done
#4 sha256:8922847ad71151ca134ff6df3b8df140fc3c267f3093bc7c6df6290e5275901c 15.73MB / 647.25MB 0.2s
#4 sha256:677076032cca0a2362d25cf3660072e738d1b96fe860409a33ce901d695d7ee8 0B / 29.53MB 0.2s
#4 sha256:677076032cca0a2362d25cf3660072e738d1b96fe860409a33ce901d695d7ee8 9.44MB / 29.53MB 0.3s

Question: What would be the best option to have image with latest bazel included

Hi people!

I see that you have both images for android sdk and bazel. What would be the best strategy to have both layers in one image?

A similar question I have for the latest gradle.

Docker image warning on Apple Silicon

This shows in Docker Desktop's "Images" tab:

I'm on MacBook Air M1.

Windows image with Android SDK bundled?

Would it be possible to get a Windows image with the Android SDK bundled? I'd like to do some integration testing on Windows that will need that. I could pull it down as part of my process, but it'd be nice if it was just there.

Support Java 9

Received this error when trying to run tests that targets Android SDK 30: java.lang.UnsupportedOperationException: Failed to create a Robolectric sandbox: Android SDK 30 requires Java 9 (have Java 8)

Example: https://cirrus-ci.com/task/4736390513557504?logs=main#L5972

Update to Android SDK 31

Hey folks,

Android 12 was released back in September and thus a new SDK version was published too. Could you please build a new image for SDK version 31?

Upgrade OpenJDK from 17 to 21

21 is the latest LTS release.

docker-images-android/sdk/tools/Dockerfile

Line 22 in f8eeb86

&& apt-get install -y openjdk-17-jdk \

NDK images

Turns out the NDK built on in the "30-ndk" image may be too new to be picked up by the current AGP versions.

A detailed table here: https://developer.android.com/studio/projects/install-ndk#default-ndk-per-agp

Should the 30-ndk image therefore:

• contain both the latest NDK versions (21.x & 20.x)
• only contain the NDK which matches the latest stable AGP?
• stay as is

Personally, I'd probably go with the first option (or better, include every latest NDK version), however such image will take up significant space.

Update focal to jammy

This docker image still uses Ubuntu 20.04 (focal) as base image. This causes problems together with https://github.com/cirruslabs/docker-images-flutter/blob/master/desktop/linux/Dockerfile, as Ubuntu focal still ships jsoncpp version 1. Any other modern distribution including Ubuntu jammy, Debian testing, Fedora or Arch ship jsoncpp version 2. All Flutter Linux builds are incompatible with desktop distributions hence.

I'd highly recommend to update to Ubuntu 22.04 LTS (jammy) hence.

Add latest Gradle to the image

Gradle is the most popular build tool used in Android. Maybe it'd make sense to use one of the gradle images as base of android-sdk:tools instead of ubuntu:22.04?

Most projects use a version from gradle-wrapper.properties though, so I'm not sure how much sense it makes.

Android SDK 34

Could you please provide an image for Android SDK 34 (Android 14)?

sdk/tools/Dockerfile

Why is `emulator` installed only on x86_64?

Code in question:

docker-images-android/sdk/tools/Dockerfile

Line 46 in 5419e5d

RUN if [[ $(uname -m) == "x86_64" ]] ; then sdkmanager emulator ; fi

Rebuild image

Hey guys,

as the new v3 API of Google requires at least fastlane in version 2.136 it would be good to push an updated build of this image to dockerhub.

Thanks in advance

Best
Patrick

Update Java version to 17

Currently the tools image installs Java 11, but Gradle 8, now stable, requires at least Java 17.

Related: cirruslabs/docker-images-flutter#278

ARM64 Support?

Using it with AMD64 it works.

Using it with ARM64 (Raspberry Bookworm) i get errors:

docker pull ghcr.io/cirruslabs/android-sdk:tools
tools: Pulling from cirruslabs/android-sdk
no matching manifest for linux/arm64/v8 in the manifest list entries

docker pull ghcr.io/cirruslabs/android-sdk:33
33: Pulling from cirruslabs/android-sdk
no matching manifest for linux/arm64/v8 in the manifest list entries

docker pull ghcr.io/cirruslabs/android-sdk:34
34: Pulling from cirruslabs/android-sdk
no matching manifest for linux/arm64/v8 in the manifest list entries

After switching to ghcr.io access to image is denied

See build log.

upgrade ndk to 23.1.7779620

Hey, version 21.3.6528147 of NDK is alright but I am hitting android/ndk#1281, any chance to rebuild with a newer NDK?