docker-gradle

Supported tags and respective Dockerfile links

• jdk8, jdk8-jammy
• jdk8-focal
• jdk8-corretto
• jdk11, jdk11-jammy
• jdk11-focal
• jdk11-alpine
• jdk11, jdk11-corretto
• jdk17, jdk17-jammy
• jdk17-focal
• jdk17-alpine
• jdk17-corretto
• jdk17-graal
• jdk17-focal-graal
• jdk21, jdk21-jammy, latest
• jdk21-alpine, alpine
• jdk21-corretto, corretto
• jdk21-graal, graal
• jdk23, jdk23-noble
• jdk23-alpine
• jdk23-corretto
• jdk23-graal
• jdk-lts-and-current
• jdk-lts-and-current-alpine
• jdk-lts-and-current-graal

lts-and-current images

Gradle's support for new Java releases historically has lagged for multiple months. This means most users wanting to use the latest Java release will need to do so using toolchains. Toolchains are documented here and here for GraalVM. The lts-and-current images provide both the latest LTS JDK and the latest (LTS or non-LTS) JDK. This allows Gradle to be launched with a supported JDK (the latest LTS release) and configure the compilation using toolchains to use the latest current JDK. This is done by putting the content below in /home/gradle/.gradle/gradle.properties.

org.gradle.java.installations.auto-detect=false
org.gradle.java.installations.auto-download=false
org.gradle.java.installations.fromEnv=JAVA_LTS_HOME,JAVA_CURRENT_HOME

The JAVA_LTS_HOME environment variable points to the path where the latest LTS JDK is installed and JAVA_CURRENT_HOME points to the latest current JDK. These may point to the same path if the latest JDK is an LTS release.

What is Gradle?

Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing websites. Gradle has been designed to support build automation across multiple languages and platforms including Java, Scala, Android, C/C++, and Groovy, and is closely integrated with development tools and continuous integration servers including Eclipse, IntelliJ, and Jenkins.

How to use this image

If you are mounting a volume and the uid/gid running Docker is not 1000, you should run as user root (-u root). root is also the default, so you can also simply not specify a user.

Building a Gradle project

Run this from the directory of the Gradle project you want to build.

Bash/Zsh

docker run --rm -u gradle -v "$PWD":/home/gradle/project -w /home/gradle/project gradle:latest gradle <gradle-task>

PowerShell

docker run --rm -u gradle -v "${pwd}:/home/gradle/project" -w /home/gradle/project gradle:latest gradle <gradle-task>

Windows CMD

docker run --rm -u gradle -v "%cd%:/home/gradle/project" -w /home/gradle/project gradle:latest gradle <gradle-task>

Note the above command runs using uid/gid 1000 (user gradle) to avoid running as root.

Reusing the Gradle cache

The local Gradle cache can be reused across containers by creating a volume and mounting it to /home/gradle/.gradle. Note that sharing between concurrently running containers doesn't work currently (see #851).

Also, currently it's not possible to override the volume declaration of the parent. So if you are using this image as a base image and want the Gradle cache to be written into the next layer, you will need to use a new user (or use the --gradle-user-home/-g argument) so that a new cache is created that isn't mounted to a volume.

docker volume create --name gradle-cache
docker run --rm -u gradle -v gradle-cache:/home/gradle/.gradle -v "$PWD":/home/gradle/project -w /home/gradle/project gradle:latest gradle <gradle-task>

Instructions for a new Gradle release

1. Run update.sh or update.ps1.
2. Commit and push the changes.
3. Update official-images (and docs if appropriate).

---