Chainguard Container for filebeat-fips

filebeat Tails and ships log files

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/filebeat-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 Filebeat Image is comparable to the official Filebeat image from Docker Hub. However, the Chainguard image does not run as the root user and contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager.

FIPS Compliance

The filebeat-fips image is built with FIPS-approved cryptographic modules, ensuring it meets relevant FIPS standards.

Getting Started

There are no actively supported Helm charts for deploying Filebeat upstream. The most recent are present here and were archived in 2023. There are, however, manifest-based deployments offered as an alternative by the upstream maintainers.

You will need to override the image properties to use the Chainguard-provided image for Filebeat. Additionally, make sure to change the image in the daemonset to the Chainguard filebeat Image.

Be aware that you can configure Filebeat to write to a specific output by setting options in the Outputs section of the filebeat.yml config file. In the manifests provided above, it can be done here.

2. The above manifests will bring Filebeat up in kube-system namespace. And you will be able to see Filebeat output in *.ndjson file in /usr/share/filebeat/output directory in the Filebeat pod.

Documentation and Resources

• Filebeat official docs

The upstream documentation doesn't currently maintain a Filebeat Helm chart, and testing with the deprecated chart requires installing additional packages (such as curl and bash) in the container.

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.