Chainguard Container for filebeat

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: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.

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'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.