Fluentd is an open source data collector, which lets you unify the data collection and consumption for a better use and understanding of data.
Dockerfile
linksThese tags have image version postfix. This updates many places so we need feedback for improve/fix the images.
Current images use fluentd v1 series.
v1.17.1-1.0
, v1.17-1
, edge
(v1.17/alpine/Dockerfile) (Deprecated)v1.17.1-debian-1.0
, v1.17-debian-1
, edge-debian
(multiarch image for arm64(AArch64) and amd64(x86_64))v1.17.1-debian-amd64-1.0
, v1.17-debian-amd64-1
, edge-debian-amd64
(v1.17/debian/Dockerfile)v1.17.1-debian-arm64-1.0
, v1.17-debian-arm64-1
, edge-debian-arm64
(v1.17/arm64/debian/Dockerfile)v1.17.1-debian-armhf-1.0
, v1.17-debian-armhf-1
, edge-debian-armhf
(v1.17/armhf/debian/Dockerfile)v1.17.1-windows-ltsc2019-1.0
, v1.17-windows-ltsc2019-1
(v1.17/windows-ltsc2019/Dockerfile)v1.17.1-windows-ltsc2022-1.0
, v1.17-windows-ltsc2022-1
(v1.17/windows-ltsc2022/Dockerfile)[!TIP] About deprecated old images, See DEPRECATED
We recommend to use debian version for production because it uses jemalloc to mitigate memory fragmentation issue.
Check fluentd-kubernetes-daemonset images.
This image is based on the popular Debian images and Alpine Linux project, available in the alpine official image.
edge
Latest released version of Fluentd.
vX.Y-A
Latest version of vX.Y
Fluentd branch.
A
will be incremented when image has major changes.
When fluentd version is updated, A is reset to 1
.
vX.Y.Z-A.B
Concrete vX.Y.Z
version of Fluentd. This tag is recommeded for the production environment.
A
will be incremented when image has major changes.
B
will be incremented when image has small changes, e.g. library update or bug fixes.
When fluentd version is updated, A.B
is reset to 1.0
.
debian
included tagThe image based on Debian Linux image.
You may use this image when you require plugins which cannot be installed on Alpine (like fluent-plugin-systemd
).
armhf
included tagThe armhf
images use ARM base images for use on devices such as Raspberry Pis.
Furthermore, the base images enable support for cross-platform builds using the cross-build tools from resin.io.
In order to build these images natively on ARM devices, the CROSS_BUILD_START
and CROSS_BUILD_END
Docker build arguments must be set to the shell no-op (:
), for example:
docker build --build-arg CROSS_BUILD_START=":" --build-arg CROSS_BUILD_END=":" -t fluent/fluentd:v1.3-onbuild-1 v1.3/armhf/alpine-onbuild
(assuming the command is run from the root of this repository).
These images/tags are kept for backward compatibility. No update anymore and don't use for new deployment. Use "current images" instead.
stable
, latest
These tags are obsolete, already removed to avoid confusing.
Use edge
, vX.Y-A
or vX.Y.Z-A.B
images instead.
vX.Y
Latest version of vX.Y
Fluentd branch.
vX.Y.Z
Concrete vX.Y.Z
version of Fluentd.
onbuild
included tagonbuild
images are deprecated. Use non-onbuild
images instead to build your image.
New images, v1.5 or later, don't provide onbuild
version.
debian
included tag, armhf
included tagSame as current images.
To create endpoint that collects logs on your host just run:
docker run -d -p 24224:24224 -p 24224:24224/udp -v /data:/fluentd/log fluent/fluentd:v1.3-debian-1
Default configurations are to:
24224
for Fluentd forward protocoldocker.**
into /fluentd/log/docker.*.log
(and symlink docker.log
)/fluentd/log/data.*.log
(and symlink data.log
)fluentd
arguments can be appended to the docker run
line
For example, to provide a bespoke config and make fluentd
verbose, then:
docker run -ti --rm -v /path/to/dir:/fluentd/etc fluent/fluentd -c /fluentd/etc/<conf> -v
The first -v
tells Docker to share '/path/to/dir' as a volume and mount it at /fluentd/etc
The -c
after the container name (fluentd) tells fluentd
where to find the config file
The second -v
is passed to fluentd
to tell it to be verbose
Use -u
option with docker run
.
docker run -p 24224:24224 -u foo -v ...
Check HOWTOBUILD explanation.
Fluentd logging driver - Docker Docs
We can't notice comments in the DockerHub so don't use them for reporting issue or asking question.
If you have any problems with or questions about this image, please contact us through a GitHub issue.