Public | Automated Build

Last pushed: 3 hours ago
Short Description
Fluentd Docker image by fluent project:
Full Description

Fluentd Docker Image

Supported tags and respective Dockerfile links

What is Fluentd?

Fluentd is an open source data collector, which lets you unify the data
collection and consumption for a better use and understanding of data.

How to use this image

To create endpoint that collectc logs on your host just run:

docker run -d -p 24224:24224 -p 24224:24224/udp -v /data:/fluentd/log fluent/fluentd

Default configurations are to:

  • listen port 24224 for Fluentd forward protocol
  • store logs with tag docker.** into /fluentd/log/docker.*.log
    (and symlink docker.log)
  • store all other logs into /fluentd/log/data.*.log (and symlink data.log)

Environment Variables

Environment variable below are configurable to control how to execute fluentd process:


This variable allows you to specify configuration file name that will be used
in -c Fluentd command line option.

If you want to use your own configuration file (without any optional plugins),
you can do it with this environment variable and Docker volumes (-v option
of docker run).

  1. Write configuration file with filename yours.conf.
  2. Execute docker run with -v /path/to/dir:/fluentd/etc
    to share /path/to/dir/yours.conf in container,
    and -e FLUENTD_CONF=yours.conf to read it.


Use this variable to specify other Fluentd command line options,
like -v or -q.

Image versions

This image is based on the popular Alpine Linux project, available in
the alpine official image.
Alpine Linux is much smaller than most distribution base images (~5MB), and
thus leads to much slimmer images in general.

Since v0.12.26, tags are separated into vX.Y.Z and vX.Y.Z-onbuild.

stable, latest

Latest version of stable Fluentd branch (currently v0.12).


Latest version of edge Fluentd branch (currently v0.14).


Latest version of vX.Y Fluentd branch.


Concrete vX.Y.Z version of Fluentd.

onbuild, xxx-onbuild

This image makes building derivative images easier.
See "How to build your own image" section for
more details.


The 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).

How to build your own image

You can build a customized image based on Fluentd's onbuild image.
Customized image can include plugins and fluent.conf file.

1. Create a working directory

We will use this directory to build a Docker image.
Type following commands on a terminal to prepare a minimal project first:

# Create project directory.
mkdir custom-fluentd
cd custom-fluentd

# Download default fluent.conf. this file will be copied to the new image.
curl > fluent.conf

# Create plugins directory. plugins scripts put here will be copied to the new image.
mkdir plugins

# Download sample Dockerfile.
curl > Dockerfile

2. Customize fluent.conf

Documentation of fluent.conf is available at

3. Customize Dockerfile to install plugins (optional)

You can install Fluentd plugins using Dockerfile.
Sample Dockerfile installs fluent-plugin-elasticsearch and
To add plugins, edit Dockerfile as following:

Apline version
FROM fluent/fluentd:onbuild

USER root

# below RUN includes two plugins as examples
# elasticsearch and record-reformer are not required
# you may customize including plugins as you wish

RUN apk add --update --virtual .build-deps \
        sudo build-base ruby-dev \
 && sudo -u fluent gem install \
        fluent-plugin-elasticsearch \
        fluent-plugin-record-reformer \
 && sudo -u fluent gem sources --clear-all \
 && apk del .build-deps \
 && rm -rf /var/cache/apk/* \

USER fluent

EXPOSE 24284
Debian version
FROM fluent/fluentd:debian-onbuild

USER root

# below RUN includes two plugins as examples
# elasticsearch and record-reformer are not required
# you may customize including plugins as you wish

RUN buildDeps="sudo make gcc g++ libc-dev ruby-dev" \
 && apt-get update \
 && apt-get install -y --no-install-recommends $buildDeps \
 && sudo -u fluent gem install \
        fluent-plugin-elasticsearch \
        fluent-plugin-record-reformer \
 && sudo -u fluent gem sources --clear-all \
    apt-get purge -y --auto-remove \
                  -o APT::AutoRemove::RecommendsImportant=false \
                  $buildDeps \
 && rm -rf /var/lib/apt/lists/* \

USER fluent

These example run apk add/apt-get install to be able to install
Fluentd plugins which require native extensions (they are removed immediately
after plugin installation).
If you're sure that plugins don't include native extensions, you can omit it
to make image build faster.

4. Build image

Use docker build command to build the image.
This example names the image as custom-fluentd:latest:

docker build -t custom-fluentd:latest ./

5. Test it

Once the image is built, it's ready to run.
Following commands run Fluentd sharing ./log directory with the host machine:

mkdir -p log
docker run -it --rm --name custom-docker-fluent-logger -v $(pwd)/log:/fluentd/log custom-fluentd:latest

Open another terminal and type following command to inspect IP address.
Fluentd is running on this IP address:

docker inspect -f '{{.NetworkSettings.IPAddress}}' custom-docker-fluent-logger

Let's try to use another docker container to send its logs to Fluentd.

docker run --log-driver=fluentd --log-opt tag="docker.{{.ID}}" --log-opt fluentd-address=FLUENTD.ADD.RE.SS:24224 python:alpine echo Hello
# and force flush buffered logs
docker kill -s USR1 custom-docker-fluent-logger

(replace FLUENTD.ADD.RE.SS with actual IP address you inspected at
the previous step)

You will see some logs sent to Fluentd.


Docker Logging |

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.

Docker Pull Command
Source Repository

Comments (10)
13 days ago

Thanks, folks!

In the curl commands above, you can use -o filename (ie, -o Dockerfile) intead of the output redirection operator.

9 months ago

The docker logscommand is available only for the json-file and journald logging drivers.

10 months ago

Sorry we can't notice the comment in the DockerHub so don't use this comment for reporting issue or asking question.
Use github repository or fluentd mailing list instead: /!forum/fluentd

a year ago

This start script helped me to finally make plugin work:


export PATH=/home/fluent/.gem/ruby/2.3.0/bin:$PATH
export GEM_PATH=/home/fluent/.gem/ruby/2.3.0:$GEM_$PATH
fluent-gem install fluent-plugin-elasticsearch
exec fluentd -c /fluentd/etc/$FLUENTD_CONF -p /fluentd/plugins $FLUENTD_OPT
a year ago

Doesn't the logging driver work with docker-compose?

I get the following error: "logs" command is supported only for "json-file" and "journald" logging drivers (got: fluentd)

a year ago

Shouldn't this container print log messages to stdout due to the stdout_filter? For me the log messages end up in the files in /fluentd/log/. But except the output of fluentd itself nothing is written to stdout in the container.
I'm not familiar with fluentd, maybe I understand something wrong?

a year ago

Thanks for the comment. I just added tags. I thought DockerHub builds the image for each github tag automatically...

2 years ago

+1 for tagging

2 years ago

I suggest to add version-specific tags. Dockerfile on this page is out of data and it doesn't show the latest version of fluentd installed in the image.

2 years ago

Can you tag specific versions (not just 'latest')? Thanks!