To support container-based development, GraalVM Community Edition container images are published in the GitHub Container Registry for each release.
There are different GraalVM Community Edition container images provided depending on the architecture and the Java version.
The images are multi-arch (aarch64 or amd64 depending on the host architecture).
Some images are GU-based (containing the GraalVM Updater tool), some are RPM-based.
All images support the installation of extra features. The following container images are available:
| Package | Description | Type |
|---|---|---|
| jdk | A size compact GraalVM Community container image with the GraalVM JDK pre-installed. | RPM-based1 |
| graalvm-ce | A GraalVM Community Edition container image with the gu utility to install additional features. |
GU-based |
| native-image | A size compact GraalVM Community container image with the Native Image support. | RPM-based1 |
| truffleruby | A size compact GraalVM Community container image with the Ruby runtime. It uses a standalone build of TruffleRuby. | Standalone2 |
| nodejs | A size compact GraalVM Community container image with the Node.js runtime. | RPM-based1 |
| graalpy | A size compact GraalVM Community container image with the GraalPy runtime. | Standalone2 |
1: RPM-based GraalVM Community container images are based on GraalVM components RPMs that are available for Oracle Linux 7, Oracle Linux 8 and Oracle Linux 9. Similar to any other available packages, you can install these components using yum on Oracle Linux 7 or microdnf on the Oracle Linux 8 and Oracle Linux 9 based images.
2: Standalone-based GraalVM Community Language container images are based on GraalVM standalone builds of specific truffle languages, these images are created as a drop-in replacement for other implementations (TruffleRuby instead of MRI Ruby), these images do not contain a java runtime.
The images are tagged with the format ghcr.io/graalvm/IMAGE_NAME:version.
The version tag defines the level of specificity.
It is recommended that the most specific tag be used, e.g., java17-22.3.1 or java17-22.3.1-b1, where the -b1 means the image required a patch and this specific build will never change.
You can pull a package by name or by name and version tag. To install GraalVM JDK from the command line, use:
$ docker pull ghcr.io/graalvm/jdk:java17-22.3.1
To use GraalVM JDK as base image in Dockerfile, use:
FROM ghcr.io/graalvm/jdk:java17-22.3.1
Read more about running GraalVM Community Edition container images here.
To allow users to control their update policy, we provide an update policy based on a tag version. To fix the image and allow no updates, you need to use a full version with a build number:
ghcr.io/graalvm/$IMAGE_NAME[:][$os_version][-$java_version][-$version][-$build_number]
For example, ghcr.io/graalvm/jdk:java17-22.3.1-b1.
You can also set an image to a specific version number that allows an update for a subversion to be pulled.
For instance, using ghcr.io/graalvm/jdk:java17-22.3, the image will be updated for 22.3.x releases, but not for 22.3.1.
Using ghcr.io/graalvm/native-image you will always get the latest update available for Native Image, the latest OS which is for now the Oracle Linux 9 and the Oracle Linux 9 slim, the latest Java version, and the latest GraalVM version.
Note some terms and restrictions that may apply to the open source technology. The container image you select and all of the software that it contains is licensed under one or more open source license that are provided in the container image. Your use of the container is subject to the terms of those licenses.