jdk-fips-preview

Chainguard Container for jdk-fips-preview

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/jdk-fips-preview:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Pre-GA Terms Apply

Pre-GA terms apply. Specifically the image tags, image specification, environment variables, command line arguments, java security policy settings may change without notice based on preview feedback and evaluations.

Available versions and variants

This image is currently available in the following image tag prefixes:

• corretto-25

Other flavors and variants are coming soon:

• openjdk-25
• adoptium-25

Please request other flavors if needed for testing

Differences relative existing bcfips images

• SUN provider no longer loaded by default
• MD5 enabled for non-security purposes only from the BC-FIPS provider
  • For reasoning see https://edu.chainguard.dev/chainguard/fips/non-approved-algorithms/
  • Can be controlled with security property setting to opt-out
  • Note MD5 is required to be enabled for maven to work in most configurations
• JKS trust store format is read-only by default
• All FIPS-specific environment variables removed
  • Instead default arguments are included in the runtime image
• Kernel entropy java.security policy snippet dropped
• Non-approved usage java.security policy snippet dropped
• Access to BC-FIPS libraries requires add-modules imports
  • Previously classpath was exported that forced bc-fips into the unnamed module, contrary to the Modular Java requirements
  • Now JDK_JAVAC_OPTIONS is set to --module-path=/usr/share/java/bouncycastle-fips --add-modules org.bouncycastle.fips.core, for your convenience
  • If your codebases uses bc-fips library APIs directly, you may need to add appropriate --add-modules in your build system to access org.bouncycastle.crypto.fips.FipsStatus, BC-TLS, BC-PGP and other modules
  • Please provide feedback if JDK_JAVAC_OPTIONS is useful or redundant
• Trust store format is explicitly set to JKS
• Key store format is explicitly set to BCFKS
• Loading trusted CA certificates supported
  • Via Custom Assembly, ask your account rep to enable
  • Via update-ca-certs
  • Via keytool with explicit provider set to SUN

Future work:

• Upcoming bc-fips 2.1.2 update will enable jlink support, with which JDK_JAVAC_OPTIONS will be removed
• There are some warnings from "[warning][cds] This file is not the one used while building the shared archive file" that we are investigating

Feedback

Please provide feedback to your account representatives or via support portal with ticket title mentioning "jdk-fips-preview feedback".

## What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with [Wolfi](https://edu.chainguard.dev/open-source/wolfi/overview?utm_source=readmes), our minimal Linux _[undistro](https://edu.chainguard.dev/open-source/wolfi/overview/#why-undistro)_.

All other Chainguard Containers are built with [Chainguard OS](https://edu.chainguard.dev/chainguard/chainguard-os/overview/?utm_source=readmes), Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

* Minimal design, without unnecessary software bloat
* Daily builds to ensure container images are up-to-date with available security patches
* [High quality build-time SBOMs](https://edu.chainguard.dev/chainguard/chainguard-images/working-with-images/retrieve-image-sboms/?utm_source=readmes) attesting to the provenance of all artifacts within the image
* [Verifiable signatures](https://edu.chainguard.dev/chainguard/chainguard-images/working-with-images/retrieve-image-sboms/) provided by [Sigstore](https://edu.chainguard.dev/open-source/sigstore/cosign/an-introduction-to-cosign/?utm_source=readmes)
* Reproducible builds with Cosign and apko ([read more about reproducibility](https://www.chainguard.dev/unchained/reproducing-chainguards-reproducible-image-builds?utm_source=readmes))

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with [a *development*, or `-dev`, variant](https://edu.chainguard.dev/chainguard/chainguard-images/about/differences-development-production/).

In all other cases, including Chainguard Containers tagged as `:latest` or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the `-dev` container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the `-dev` variant into a more minimal production image.

## Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use [Custom Assembly](https://edu.chainguard.dev/chainguard/chainguard-images/features/ca-docs/custom-assembly/) to add packages, either through the Console, `chainctl`, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in [your Organization's list of images](https://console.chainguard.dev/images/organization), and click on the **Customize image** button at the top of the page.

## Learn More

Refer to our Chainguard Containers documentation on [Chainguard Academy](https://edu.chainguard.dev/?utm_source=readmes). Chainguard also offers [VMs](https://www.chainguard.dev/vms?utm_source=readmes) and [Libraries](https://www.chainguard.dev/libraries?utm_source=readmes) — [contact us](https://www.chainguard.dev/contact?utm_source=readmes) for access.
 

## Trademarks

_This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies._