Last changed
docker pull cgr.dev/chainguard/jdk
Need access to a specific version? Contact us.
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InMinimal Wolfi-based Java JDK image using OpenJDK. Used for compiling Java applications.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
Like most available alternatives, Chainguard's JDK image is built directly from the OpenJDK project. The Chainguard JDK image has few-to-zero CVEs and does not run as the root user.
The JDK is the standard development system for a Java application. It is used for compiling and packaging Java applications, which are then run on a JRE.
This section outlines how you can build a Java application with the Chainguard JDK Image.
Start by creating a sample Java class named HelloWolfi
:
Then create a multistage Dockerfile, adding the Java class you just created:
Following that, you can build the image:
Note that this example tags the image with my-java-app
. You can now run the image by referencing this tag, as in the following command:
Using a Chainguard Image as part of a CI/CD system like Jenkins might also be a useful option. With the Jenkins Docker agent, you can define multiple steps that use different Chainguard Images. The following is an example using the Chainguard JDK image as part of a Jenkins pipeline:
For a full reference on using various images in a Jenkins pipeline, please refer to the Jenkins documentation.
A less common, but powerful, use case for the JDK image is creating an optimized custom JRE for your Java application. This involves using jdeps
to produce the information about the Java modules being used and subsequently using jlink
to analyze your application to eliminate all module code not being used by your application. This can create a drastically smaller JRE for a particular application.
Keep in mind that a JRE produced this way is a fit-for-purpose JRE, and is not broadly usable.
For reference, here are two additional articles describing the use of jlink
to create optimized application images:
The latest builds of Chainguard's JRE image pass the TCK for OpenJDK Java 21.0.3 and Java 22.0.1 as provided by OpenJDK Community TCK License Agreement (OCTLA) and are Java Compatibility Kit (JCK) conformant.
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
BSD-3-Clause
Bitstream-Vera
FTL
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.