tomcat-iamguarded

packaged by Chainguard

Chainguard Container for tomcat-iamguarded

Apache Tomcat is 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:latest

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

Overview

Tomcat iamguarded is a security-hardened, iamguarded-compatible variant of Apache Tomcat designed to be deployed using its companion iamguarded Helm chart. Tomcat is installed into the iamguarded layout under /opt/iamguarded/tomcat (with the JDK at /opt/iamguarded/java), runs as the non-root tomcat user (UID/GID 1001), and boots via the iamguarded entrypoint scripts.

A FIPS 140-3 build is available as the separate tomcat-iamguarded-fips image.

Helm Chart Installation

The Tomcat iamguarded Helm chart is delivered through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/tomcat

Basic Installation

Once authenticated (see below) you can install the chart with standard Helm commands and your organization name:

helm install tomcat-iamguarded oci://cgr.dev/$ORGANIZATION/iamguarded-charts/tomcat \
  --set "global.org=$ORGANIZATION"

Important: Replace $ORGANIZATION with your Chainguard organization name. The default organization in the chart values is chainguard-private, which must be changed to match your organization.

Registry Configuration

For users who mirror images to custom repositories, use global.imageRegistry to override the default cgr.dev, or set the per-image registry, repository, and digest values (including metrics.jmx.image and volumePermissions.image) directly. See the chart's values.yaml (helm show values) for the full set of options.

Authentication

For detailed instructions on configuring authentication and pull credentials for iamguarded images, refer to How to Use Chainguard Helm Charts.

Best Practices

1. Pin to digest: while charts follow the same tagging scheme as Chainguard images, pin to a specific chart digest to prevent unexpected updates. The digest is shown in the output of helm pull oci://cgr.dev/$ORGANIZATION/iamguarded-charts/tomcat.
2. Review default values: the chart provides security-minded defaults that may not be production-ready for all use cases. Review helm show values for the full range of options.

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.