terragrunt-fips

Chainguard Container for terragrunt-fips

A cloud infrastructure orchestration tool that supports OpenTofu/Terraform.

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/terragrunt-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

Note on Terraform/OpenTofu Support: The Terragrunt maintainers do not maintain the Docker images and actively recommend OpenTofu over Terraform. We provide both options as separate image tags, to meet different organizational requirements: OpenTofu variants for open-source licensing needs (MPL-2.0) and Terraform variants for teams accepting BUSL-1.1 terms.

FIPS Support

The terragrunt-fips Chainguard Image ships with FIPS-validated cryptographic modules. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy

Image Variants and Tags

Terragrunt requires either Terraform (BUSL-1.1 licensed) or OpenTofu (MPL-2.0 licensed) as a runtime dependency to operate. The Chainguard FIPS image provides these as separate image tags with FIPS-validated binaries, documented below:

FIPS-Enabled Variants

1. Base Terragrunt FIPS

   • Tag: latest-fips
   • FIPS-validated Terragrunt without Terraform or OpenTofu
   • For building custom images or adding your own FIPS-validated IaC tool version
   • Example: cgr.dev/ORGANIZATION/terragrunt:latest-fips

2. Terragrunt with Terraform FIPS

   • Tags: X.Y.Z-fips (version number) or tfX.Y.Z-fips (explicit prefix)
   • FIPS-validated Terragrunt + FIPS-validated Terraform X.Y.Z
   • Important: Terraform is BUSL-1.1 licensed with commercial use restrictions
   • Example: cgr.dev/ORGANIZATION/terragrunt:X.Y.Z-fips or cgr.dev/ORGANIZATION/terragrunt:tfX.Y.Z-fips

3. Terragrunt with OpenTofu FIPS

   • Tags: otfX.Y.Z-fips
   • FIPS-validated Terragrunt + FIPS-validated OpenTofu X.Y.Z
   • OpenTofu is MPL-2.0 licensed with no commercial restrictions
   • Example: cgr.dev/ORGANIZATION/terragrunt:otfX.Y.Z-fips

Tag Format

• latest-fips - Base Terragrunt only with FIPS validation
• X.Y.Z-fips - Terragrunt with Terraform X.Y.Z FIPS
• tfX.Y.Z-fips - Terragrunt with Terraform X.Y.Z FIPS, explicit prefix
• otfX.Y.Z-fips - Terragrunt with OpenTofu X.Y.Z FIPS

Choosing the Right Variant

• Choose latest-fips if you're building a custom image with specific tool versions or using Terragrunt standalone with FIPS compliance
• Choose Terraform FIPS tags (X.Y.Z-fips or tfX.Y.Z-fips) if you need Terraform with FIPS validation, accept BUSL-1.1 licensing terms and are okay with the Terraform version rolling forward with image updates
• Choose OpenTofu FIPS tags (otfX.Y.Z-fips) if you need open-source licensing (MPL-2.0) with FIPS compliance and are okay with the OpenTofu version rolling forward with image updates

Getting Started

Terragrunt is a thin wrapper for Terraform/OpenTofu that provides extra tools for keeping configurations DRY, working with multiple modules, and managing remote state.

Basic Usage

Mount the local volume containing your Terragrunt project and terragrunt.hcl:

# Using base FIPS variant (Terragrunt only)
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:latest-fips --version

# Using Terraform FIPS variant
# Preview changes
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:X.Y.Z-fips plan
# Apply changes
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:X.Y.Z-fips apply

# Or with explicit prefix
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:tfX.Y.Z-fips plan

# Using OpenTofu FIPS variant (recommended for open-source)
# Preview changes
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:otfX.Y.Z-fips plan
# Apply changes
docker run --rm -v $(pwd):/apps -w /apps cgr.dev/ORGANIZATION/terragrunt:otfX.Y.Z-fips apply

Using in Kubernetes

Terragrunt does not provide a Helm Chart or Kubernetes Operator. Their documentation suggests running a batch Job for scheduling:

apiVersion: batch/v1
kind: Job
metadata:
  name: infrastructure-deploy
spec:
  template:
    spec:
      restartPolicy: Never
      containers:
      - name: terragrunt
        image: cgr.dev/ORGANIZATION/terragrunt:otfX.Y.Z-fips
        command: ["terragrunt"]
        args: ["apply", "-auto-approve"]
        workingDir: /apps
        volumeMounts:
        - name: terraform-code
          mountPath: /apps
      volumes:
      - name: terraform-code
        configMap:
          name: terraform-code

Documentation and Resources

For more information about Terragrunt, refer to:

• Terragrunt Official Documentation
• Terragrunt Quick Start Guide
• GitHub Repository

For OpenTofu migration and documentation:

• OpenTofu Documentation
• Migration Guide

For FIPS compliance information:

• FIPS-enabled Chainguard Images Guide
• NIST FIPS 140-2 Standards

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.