readystack/fluentbit repository overview

⁠Fluent Bit

readystack/fluentbit:v5.1.5-CE-ubuntu24.04-r3

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/fluentbit/recipe⁠
• Upstream source at this release's pinned commit (v5.1.5): https://github.com/fluent/fluent-bit/tree/0039c4f0d1b530bedd8448df2fa4c301d58a5b91⁠
• Product page: https://readystack.dev/products/fluentbit⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/fluentbit⁠
• Release history (JSON): https://readystack.dev/api/releases/fluentbit⁠
• Defect record: https://readystack.dev/defects.html?product=fluentbit⁠
• Today's scan: https://readystack.dev/products/fluentbit#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=fluentbit⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/fluent/fluent-bit v5.1.5 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Operations and platform teams who collect logs, metrics and traces from servers, containers and devices.

Why: Fluent Bit is a lightweight telemetry agent. It collects logs, metrics and traces from many sources, filters and processes them, and forwards them to the destinations you choose.

Use case: A team runs applications on many servers and containers and wants all their logs in one central store. Fluent Bit on each host reads the log files, parses and filters the records, and forwards them to the team's log backend, while using little CPU and memory on the hosts.

About the upstream project, written from its own description: https://github.com/fluent/fluent-bit⁠ · https://docs.fluentbit.io/manual/about/what-is-fluent-bit⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:cb71df56f2b19c7fcca62dcae08e3285ea9cf502ce59cfe7a78d595d32a88487 on 2026-11-09.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/fluentbit⁠
• ReadyStack release check — passed at release on 2026-11-09: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:cb71df56f2b19c7fcca62dcae08e3285ea9cf502ce59cfe7a78d595d32a88487; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/fluentbit:v5.1.5-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (fluentbit).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v5.1.5-CE-ubuntu24.04-r3 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/fluentbit:v5.1.5-CE-ubuntu24.04-r3

# ✗ unsupported (do not pull)
docker pull readystack/fluentbit:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/fluentbit:v5.1.5-CE-ubuntu24.04-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running one C binary, /fluent-bit/bin/fluent-bit, compiled from the upstream source with every bundled library built in. It is a log, metrics and traces processor and forwarder: it reads from the inputs you configure, filters, and sends to the outputs you configure. It has no database, no web UI and no user accounts. It runs as the non-root user fluentbit.

docker run -d --name fluentbit -p 127.0.0.1:2020:2020 readystack/fluentbit:v5.1.5-CE-ubuntu24.04-r3

The default configuration is upstream's demo pipeline: it reads CPU usage every second and prints the records to the container's standard output (docker logs fluentbit). Mount your own configuration over /fluent-bit/etc/fluent-bit.conf for a real pipeline. Publishing port 2020 on 127.0.0.1 keeps the unauthenticated monitoring API off other hosts.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/fluentbit⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:9fb8675d6ce91ab7cddfc1fb4393885a4ae0dca975fecc0c5ffc33233458c4e3 on 2026-11-09.

— ReadyStack · readystack.dev