instrumentisto-haraka-fips

packaged by Chainguard

Chainguard Container for instrumentisto-haraka-fips

Haraka SMTP server (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/instrumentisto-haraka-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 instrumentisto-haraka-fips Chainguard Container is a drop-in replacement for the upstream instrumentisto/haraka image. It provides the same functionality with the following differences:

• Runs as a non-root user (65532) by default (the upstream image runs as root) and listens on the standard SMTP port 25.
• Does not ship a package manager. The upstream image's APK_INSTALL_PACKAGES entrypoint option (runtime apk add) is therefore not supported on the default runtime image. To add OS packages at runtime, use the -dev image variant (e.g. cgr.dev/ORGANIZATION/instrumentisto-haraka-fips:latest-dev), which includes the apk package manager. A -dev variant is published for both the standard and FIPS images.

FIPS Support

The instrumentisto-haraka-fips Chainguard Container routes all cryptography through the FIPS-validated OpenSSL provider module, configured via openssl-config-fipshardened, so TLS and STARTTLS use only FIPS-approved algorithms. Haraka has no cryptography of its own, so no source changes are required. The optional CRAM-MD5 SASL mechanism relies on HMAC-MD5 and is therefore unavailable under FIPS — use AUTH PLAIN or AUTH LOGIN over STARTTLS instead. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

You can run Haraka directly with Docker:

docker run -d \
  -p 25:25 \
  cgr.dev/ORGANIZATION/instrumentisto-haraka-fips:latest

This starts Haraka with the SMTP server listening on port 25.

The configuration tree lives at /etc/haraka (the HARAKA_HOME directory). Mount your own configuration over it, or set the following environment variables, which the entrypoint honors at container start:

• HARAKA_INSTALL_PLUGINS — comma-separated Haraka npm plugins to install at start (installed under HARAKA_HOME).

Documentation and Resources

• Haraka Official Documentation
• Haraka GitHub Repository
• instrumentisto/haraka Docker wrapper
• Chainguard Academy

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.