Chainguard Container for maven-fips

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/maven-fips:latest

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

Tags and FIPS specific notes

The tags are in the form of <MAVEN_VERSION>-jdk<OPENJDK_VERSION>[-dev], such that one can track 3.9-jdk21 for Maven 3.9.x with OpenJDK 21.

The -dev variants contain jmods, thus suitable to use jlink.

Note, exclude bc-fips.jars /usr/share/java/bouncycastle-fips/ module-path from jlink, as jlink is unable to link signed jars. Instead ensure that --module-path=/usr/share/java/bouncycastle-fips is used at runtime, with such path copied from either this image, or jdk-fips or jre-fips images.

OpenJDK 8 is not currently supported for FIPS, thus with this image, one must target at least JDK 11 during build.

Please see specification tab for the extra variables set to ensure Maven and Java are operating in FIPS mode.

Using Maven

Chainguard Maven images come with different versions of OpenJDK, ensure you choose the correct image tag for your application needs. In these examples we will use a Chainguard Maven image based on OpenJDK 21.

Check the maven version

docker run --rm --platform=linux/amd64 cgr.dev/chainguard/maven-fips:3.9-jdk21 --version

Examples

SpringBoot

Visit https://start.spring.io

Select the following options:

1. Project: select Maven Project
2. Spring Boot: latest GA version, e.g. 2.7.5
3. Project Metadata: populate your application details
4. Packaging: select your packaging. For this demo, we'll use jar
5. Java: select Java version, e.g. 21 that matches the OpenJDK image version we are building with
6. Dependencies: choose your dependencies, e.g. Spring Web
7. Generate: Hit that generate button!

Go to your downloaded zip file, unzip

mkdir ~/chainguard-sb
cd chainguard-sb
mv ~/Downloads/demo.zip .
unzip demo.zip
cd demo

You now have your generated Spring Boot application souce code. Now let's build it.

docker run --platform=linux/amd64 --rm -v ${PWD}:/home/build cgr.dev/chainguard/maven-fips:3.9-jdk21 clean install

Check to see your compiled jar file

find target -name "*.jar"

You should see...

target/demo-0.0.1-SNAPSHOT.jar

Let's run the application using the Chainguard OpenJDK JRE image. Note there's a few things happening here and this is just for test purposes, see section below for more real world scenarios.

Choose the Chainguard OpenJDK JRE image tag that matches your application's Java version selected when generating your Spring Boot application above.

docker run --platform=linux/amd64 --rm -p 8080:8080 -v ${PWD}/target:/app/ cgr.dev/chainguard/jre-fips:openjdk-21 -jar /app/demo-0.0.1-SNAPSHOT.jar

Now visit the Spring Boot Application in your browser using the same port mapped in the docker command above.

e.g http://localhost:8080/

Note this is the expected Spring Whitelabel error page.

Multistage Dockerfile

The steps above are useful to test Chainguard images however, we can now create a multistage Dockerfile that will build a smaller image to run our demo application.

First create a .dockerignore file so we don't copy the generated maven ./target folder from the steps above into the multistage docker build. This helps avoid any permission errors during the build.

cat <<EOF >>.dockerignore
target/
EOF

Next create the multistage Dockerfile

cat <<EOF >>Dockerfile
FROM cgr.dev/chainguard/maven-fips:3.9-jdk21

WORKDIR /home/build

COPY . ./

RUN mvn install

FROM cgr.dev/chainguard/jre-fips:openjdk-21

COPY --from=0 /home/build/target/demo-*.jar /app/demo.jar

CMD ["-jar", "/app/demo.jar"]
EOF

Build your application image

docker build --platform=linux/amd64 -t my-chainguard-springboot-app .

Now run your application

docker run --platform=linux/amd64 --rm -p 8080:8080 my-chainguard-springboot-app

Again visit the Spring Boot Whitelabel page in your browser

e.g. http://localhost:8080/

What's inside?

Now let's take a closer look at your newly built image.

Check the size of your image, as this is based on Chainguard images it will only contain the Linux packages required to run your application. The reduces the number of packages that can be affected by CVEs.

docker images | grep my-chainguard-springboot-app

You can also check for vulnerabilities using your favorite scanner.

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.