Chainguard Container for bash-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/bash-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

The Chainguard bash-fips container image is comparable to the upstream GNU Bash shell with FIPS-validated cryptographic libraries.

FIPS Support

This Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Run interactive bash commands:

docker run --rm cgr.dev/ORGANIZATION/bash-fips:latest -c "echo 'Hello from FIPS bash'"

Execute a bash script by mounting it into the container:

cat > script.sh <<EOF
#!/bin/bash
echo "FIPS-enabled bash script running"
echo "Current date: \$(date)"
EOF

chmod +x script.sh
docker run --rm -v $(pwd)/script.sh:/script.sh cgr.dev/ORGANIZATION/bash-fips:latest /script.sh

FIPS-enabled bash script running
Current date: Tue Jun 17 20:01:59 UTC 2025

You can also test that FIPS mode is active with the following command:

docker run --rm cgr.dev/ORGANIZATION/bash-fips:latest -c "openssl-fips-test"

This uses Chainguard's openssl-fips-test tool to test whether or not OpenSSL is properly configured to use its FIPS module:

Checking OpenSSL lifecycle assurance.
*** Running check: FIPS module is available...
    HMAC : (KAT_Integrity) : Pass
    SHA1 : (KAT_Digest) : Pass
    SHA2 : (KAT_Digest) : Pass
    [... additional validation tests ...]
*** Running check: EVP_default_properties_is_fips_enabled returns true... passed.
*** Running check: verify unapproved cryptographic routines are not available by default (e.g. MD5)... passed.

Lifecycle assurance satisfied.

Documentation and Resources

• GNU Bash Documentation
• FIPS-enabled Chainguard Containers Guide

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.