Chainguard Container for fluent-bit-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/fluent-bit-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 Fluent Bit image is meant to serve as a drop-in replacement for the official Fluent Bit image from Docker Hub. Like most other Chainguard Images, this image has few-to-zero CVEs and does not run as the root user.

Getting Started

Run a Fluent Bit instance that will receive messages over TCP port 24224 through the Forward protocol, and send the messages to the STDOUT interface in JSON format every second:

docker run -p 127.0.0.1:24224:24224 cgr.dev/ORGANIZATION/fluent-bit-fips /usr/bin/fluent-bit -i forward -o stdout -p format=json_lines -f 1

In a separate terminal window, start a separate container that will send a test message. This time the Docker container will use the Fluent output protocol as the logging driver:

docker run --log-driver=fluentd -t ubuntu echo "Testing a log message"

In the Fluent Bit container output in the first terminal, this second container will print a new entry to stdout at the end of the output, like this:

Fluent Bit v2.2.1
* Copyright (C) 2015-2023 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2024/12/03 13:16:12] [ info] [fluent bit] version=2.2.1, commit=842a48223b, pid=1
[2024/12/03 13:16:12] [ info] [storage] ver=1.5.1, type=memory, sync=normal, checksum=off, max_chunks_up=128
[2024/12/03 13:16:12] [ info] [cmetrics] version=0.6.6
[2024/12/03 13:16:12] [ info] [ctraces ] version=0.4.0
[2024/12/03 13:16:12] [ info] [input:forward:forward.0] initializing
[2024/12/03 13:16:12] [ info] [input:forward:forward.0] storage_strategy='memory' (memory only)
[2024/12/03 13:16:12] [ info] [input:forward:forward.0] listening on 0.0.0.0:24224
[2024/12/03 13:16:12] [ info] [sp] stream processor started
[2024/12/03 13:16:12] [ info] [output:stdout:stdout.0] worker #0 started
{"date":1733231822.0,"source":"stdout","log":"Testing a log message\r","container_id":"f142171cc239a9a51e9dc75f2ca603183293514e625cbef50906e9256be2f0a5","container_name":"/intelligent_gagarin"}

You can instead deploy Fluent Bit as a Helm chart by running the following:

helm repo add fluent https://fluent.github.io/helm-charts
helm repo update

Then, create a YAML values file with the following command:

cat > values.yaml <<EOF
image:
  repository: cgr.dev/ORGANIZATION/fluent-bit-fips
  tag: latest

command:
  - /usr/bin/fluent-bit

EOF

Next, install it with the following command:

helm upgrade --install fluent-bit -f values.yaml fluent/fluent-bit

Documentation and Resources

• Fluent Bit official documentation

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.