Fluent Bit container images are available on Docker Hub ready for production usage. Current available images can be deployed in multiple architectures.

Tags and Versions

The following table describe the tags are available on Docker Hub fluent/fluent-bit repository:


Manifest Architectures



x86_64, arm64v8, arm32v7

Latest release of 1.4.x series.


x86_64, arm64v8, arm32v7

Release v1.4.6

1.4-debug, 1.4.6-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.5

1.4-debug, 1.4.5-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.4

1.4-debug, 1.4.4-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.3

1.4-debug, 1.4.3-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.2

1.4-debug, 1.4.2-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.1

1.4-debug, 1.4.1-debug


v1.4.x releases + Busybox


x86_64, arm64v8, arm32v7

Release v1.4.0

1.4-debug, 1.4.0-debug


v1.4.x releases + Busybox

It's strongly suggested that you always use the latest image of Fluent Bit.

Multi Architecture Images

Our x86_64 stable image is based in Distroless focusing on security containing just the Fluent Bit binary and minimal system libraries and basic configuration. Optionally, we provide debug images for x86_64 which contains Busybox that can be used to troubleshoot or testing purposes.

In addition, the main manifest provides images for arm64v8 and arm32v7 architectures. From a deployment perspective there is no need to specify an architecture, the container client tool that pulls the image gets the proper layer for the running architecture.

For every architecture we build the layers using the following base images:


Base Image






Getting Started

Download the last stable image from 1.4 series:

$ docker pull fluent/fluent-bit:1.4

Once the image is in place, now run the following (useless) test which makes Fluent Bit measure CPU usage by the container:

$ docker run -ti fluent/fluent-bit:1.4 /fluent-bit/bin/fluent-bit -i cpu -o stdout -f 1

That command will let Fluent Bit measure CPU usage every second and flush the results to the standard output, e.g:

Fluent-Bit v1.4.x
Copyright (C) Treasure Data

[2019/10/01 12:29:02] [ info] [engine] started
[0] cpu.0: [1504290543.000487750, {"cpu_p"=>0.750000, "user_p"=>0.250000, "system_p"=>0.500000, "cpu0.p_cpu"=>0.000000, "cpu0.p_user"=>0.000000, "cpu0.p_system"=>0.000000, "cpu1.p_cpu"=>1.000000, "cpu1.p_user"=>0.000000, "cpu1.p_system"=>1.000000, "cpu2.p_cpu"=>1.000000, "cpu2.p_user"=>1.000000, "cpu2.p_system"=>0.000000, "cpu3.p_cpu"=>0.000000, "cpu3.p_user"=>0.000000, "cpu3.p_system"=>0.000000}]


Why there is no Fluent Bit Docker image based on Alpine Linux ?

Alpine Linux uses Musl C library instead of Glibc. Musl is not fully compatible with Glibc which generated many issues in the following areas when used with Fluent Bit:

  • Memory Allocator: to run Fluent Bit properly in high-load environments, we use Jemalloc as a default memory allocator which reduce fragmentation and provides better performance for our needs. Jemalloc cannot run smoothly with Musl and requires extra work.

  • Alpine Linux Musl functions bootstrap have a compatibility issue when loading Golang shared libraries, this generate problems when trying to load Golang output plugins in Fluent Bit.

  • Alpine Linux Musl Time format parser does not support Glibc extensions

  • Maintainers preference in terms of base image due to security and maintenance reasons are Distroless and Debian.

Where 'latest' Tag points to ?

Our Docker containers images are deployed thousands of times per day, we take security and stability very seriously.

The latest tag most of the time points to the latest stable image. When we release a major update to Fluent Bit like for example from v1.3.x to v1.4.0, we don't move latest tag until 2 weeks after the release. That give us extra time to verify with our community that everything works as expected.

Last updated