Alpine Android Docker Images

Variants

There are two variants of the image:

• JDK8 images are based on adoptopenjdk/openjdk8:alpine (JDK 8u282-b08) and uses the tag's suffix -jdk8.
• JDK11 images are based on adoptopenjdk/openjdk11:alpine (JDK 11.0.10+9) and uses the tag's suffix -jdk11.

Which one should I use?

The recommended version is JDK8 if you are not using AGP v7.0.0+ or you are using DataBinding with a version of AGP prior to v7.0.0. Otherwise you must use JDK11 version because AGP v7.0.0+ will only work with version 11+ of the JDK.

If you want to use a JDK11 image with a version of AGP prior to v7, remember that JAXB is not included and you must add the following dependencies if using DataBinding:

// In Groovy
implementation "org.glassfish.jaxb:jaxb-runtime:2.3.3"
// or in Kotlin DSL
implementation("org.glassfish.jaxb:jaxb-runtime:2.3.3")

Tagging

📝 The tags latest and android-XX will be using the JDK8 base image for one year after AGP 7.0.0 is released to avoid problems with currents CI/CD configurations. That date is yet TBD. After that date, if you want to continue to use JDK8, you must update your configuration with the corresponding tag.

⚠️ Android 12 is in a preview state. Preview versions are tagged differently using the letter of the version instead the API level.

Versioning

Since January 1st 2021, new versions now include the date it was published so is possible to revert to a previous version. The versioning only applies to tags with the JDK version specified. The tag's format is: android-XX-jdkZZ-vYYYY.MM.DD, where:

• XX is the API level.
• ZZ is the version of the JDK.
• YYYY is the year of the release version.
• MM is the month of the year of the release version with leading zeros.
• DD is the day of the month of the release version with leading zeros.

A valid example would be android-30-jdk11-v2021.01.01. Here are listed all the versions.

📝 The versioning is not available for alpine-android-base.

Content

RUN sdkmanager <list-of-packages>

RUN apk add --no-cache <list-of-packages>

Containers registries

Because of the DockerHub rate limits, the image is now in three different containers registries:

• DockerHub: Base Image and Android Image.
• GitHub Container Registry: Base Image and Android Image.
• Quay: Base Image and Android Image.

Pulling from the different registries

Replace <tag> with one of the current available tags.

DockerHub pulling

You can pull a specific Docker image from DockerHub with the following command:

docker pull alvrme/alpine-android-base:<tag>

docker pull alvrme/alpine-android:<tag>

GHCR pulling

You can pull a specific Docker image from GitHub Container Registry with the following command:

docker pull ghcr.io/alvr/alpine-android-base:<tag>

docker pull ghcr.io/alvr/alpine-android:<tag>

Quay pulling

You can pull a specific Docker image from Quay with the following command:

docker pull quay.io/alvr/alpine-android-base:<tag>

docker pull quay.io/alvr/alpine-android:<tag>

Use as Base Image

Replace <tag> with one of the current available tags.

DockerHub base image

You can use the Docker images from DockerHub as a base image for creating a new one:

FROM alvrme/alpine-android-base:<tag>

FROM alvrme/alpine-android:<tag>

GHCR base image

You can use the Docker images from GitHub Container Registry as a base image for creating a new one:

FROM ghcr.io/alvr/alpine-android-base:<tag>

FROM ghcr.io/alvr/alpine-android:<tag>

Quay base image

You can use the Docker images from Quay as a base image for creating a new one:

FROM quay.io/alvr/alpine-android-base:<tag>

FROM quay.io/alvr/alpine-android:<tag>

Run container

Replace <tag> with one of the current available tags.

The command below will create a new container based on the specific image. It will open in the /home/android directory and the various available commands in the PATH will be able to be executed. Once the container is closed, it will be deleted. To keep the container after closing it, you have to remove --rm from the command.

DockerHub run container

Run the container from the DockerHub image:

docker run --rm -it alvrme/alpine-android-base:<tag>

docker run --rm -it alvrme/alpine-android:<tag>

GHCR run container

Run the container from the GitHub Container Registry image:

docker run --rm -it ghcr.io/alvr/alpine-android-base:<tag>

docker run --rm -it ghcr.io/alvr/alpine-android:<tag>

Quay run container

Run the container from the Quay image:

docker run --rm -it quay.io/alvr/alpine-android-base:<tag>

docker run --rm -it quay.io/alvr/alpine-android:<tag>

Extras

The base image also includes the extras command that contains small utilities that are not installed by default, since their use is not widespread.

These extras are executed with the command extras <command> and are the following

Fastlane

fastlane is a tool for iOS and Android developers to automate tedious tasks like generating screenshots, dealing with provisioning profiles, and releasing your application. Visit their documentation for more information.

This command allows you to install fastlane. There are two variants:

extras fastlane

This command allows you to install the latest version of fastlane. If you want to use a specific version, the command is as follows:

extras fastlane <version>

Extending from Alpine Android Base

Read more here

Difference between Alpine Android and Alpine Android Base

The main difference between Alpine Android and Alpine Android Base is that the first one includes the corresponding build-tools and platforms;android versions. All Alpine Android versions share 95% of the code. Using a base image with the common part makes it easier to maintain.