tomcat-iamguarded-fips

packaged by Chainguard

Chainguard Container for tomcat-iamguarded-fips

FIPS variant of Apache Tomcat, an open source implementation of the Jakarta Servlet, JSP, and WebSocket specifications.

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

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

Compatibility Notes

This is a FIPS 140-3, iamguarded-compatible variant of Apache Tomcat, designed to be deployed using its companion iamguarded Helm chart. It differs from the upstream and standard Chainguard Tomcat images in the following ways:

Installation paths

Tomcat is installed into the iamguarded layout under /opt/iamguarded/tomcat, with the JDK exposed at /opt/iamguarded/java. The entrypoint and command (/opt/iamguarded/scripts/tomcat/entrypoint.sh and run.sh) and the PATH are configured for this layout.

User and permissions

The image runs as UID/GID 1001 (tomcat, non-root). Tomcat's writable directories (conf, logs, temp, work, and /iamguarded/tomcat/webapps) are owned by that account.

FIPS Support

These images are built with FIPS 140-3 validated cryptographic modules to meet compliance requirements for regulated industries and government applications.

The JVM uses the BouncyCastle FIPS provider rather than the default JSSE providers: JAVA_TOOL_OPTIONS places the bcfips modules on the module path and JDK_JAVA_OPTIONS sets the FIPS truststore type. The image also includes openssl-config-fipshardened, so OpenSSL-backed TLS/SSL operations use FIPS-validated cryptography.

Deployment considerations

When deploying FIPS images, ensure your Kubernetes cluster and underlying infrastructure meet FIPS compliance requirements. The FIPS images provide container-level cryptographic compliance, but end-to-end FIPS compliance requires proper configuration at all layers of your infrastructure.

FIPS images are designed for environments with strict cryptographic compliance requirements. If your organization does not have FIPS compliance requirements, the standard iamguarded Tomcat image provides the same functionality with a smaller footprint.

Documentation and Resources

• Apache Tomcat Documentation
• Apache Tomcat 11.0 Documentation
• Bitnami Tomcat Helm Chart (upstream)

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, 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 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 development, or -dev, variant.

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 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, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us 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.