Quick reference

Maintained by:
Gradle, Inc.
Where to get help:
Gradle Community Slack, Gradle Community Forum, Docker Community Slack⁠, Server Fault⁠, Unix & Linux⁠, Stack Overflow⁠

Supported tags and respective `Dockerfile` links

Quick reference (cont.)

Where to file issues:
https://github.com/gradle/docker-gradle/issues
Supported architectures: (more info)
amd64, arm32v7, arm64v8, ppc64le, riscv64, s390x
Published image artifact details:
repo-info repo's repos/gradle/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/gradle label
official-images repo's library/gradle file (history)
Source of this description:
docs repo's gradle/ directory (history)

What is Gradle?

Gradle is a fast, dependable, and adaptable open-source build automation tool with an elegant and extensible declarative build language.

How to use this image

Run a Gradle task

From your project directory:

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

Replace <task> with your desired Gradle task, e.g., build.

Image Variants

The gradle images come in many flavors, each designed for a specific use case.

`gradle:<version>`

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of Ubuntu and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.

`gradle:<version>-alpine`

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's gradle/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

README.md 25 KB 永久連結 文件歷史 原始文件