See also dockerhub tags page: https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset/tags
v1.12.0-debian-azureblob-1.1,v1.12-debian-azureblob-1
docker-image/v1.12/debian-azureblob/Dockerfilev1.12.0-debian-elasticsearch7-1.0,v1.12-debian-elasticsearch7-1,v1-debian-elasticsearch
docker-image/v1.12/debian-elasticsearch7/Dockerfilev1.12.0-debian-elasticsearch6-1.0,v1.12-debian-elasticsearch6-1
docker-image/v1.12/debian-elasticsearch6/Dockerfilev1.12.0-debian-loggly-1.0,v1.12-debian-loggly-1
docker-image/v1.12/debian-loggly/Dockerfilev1.12.0-debian-logentries-1.0,v1.12-debian-logentries-1
docker-image/v1.12/debian-logentries/Dockerfilev1.12.0-debian-cloudwatch-1.1,v1.12-debian-cloudwatch-1
docker-image/v1.12/debian-cloudwatch/Dockerfilev1.12.0-debian-stackdriver-1.0,v1.12-debian-stackdriver-1
docker-image/v1.12/debian-stackdriver/Dockerfilev1.12.0-debian-s3-1.0,v1.12-debian-s3-1
docker-image/v1.12/debian-s3/Dockerfilev1.12.0-debian-syslog-1.0,v1.12-debian-syslog-1
docker-image/v1.12/debian-syslog/Dockerfilev1.12.0-debian-forward-1.0,v1.12-debian-forward-1
docker-image/v1.12/debian-forward/Dockerfilev1.12.0-debian-gcs-1.0,v1.12-debian-gcs-1
docker-image/v1.12/debian-gcs/Dockerfilev1.12.0-debian-graylog-1.0,v1.12-debian-graylog-1
docker-image/v1.12/debian-graylog/Dockerfilev1.12.0-debian-papertrail-1.0,v1.12-debian-papertrail-1
docker-image/v1.12/debian-papertrail/Dockerfilev1.12.0-debian-logzio-1.0,v1.12-debian-logzio-1
docker-image/v1.12/debian-logzio/Dockerfilev1.12.0-debian-kafka-1.0,v1.12-debian-kafka-1
docker-image/v1.12/debian-kafka/Dockerfilev1.12.0-debian-kafka2-1.0,v1.12-debian-kafka2-1
docker-image/v1.12/debian-kafka2/Dockerfilev1.12.0-debian-kinesis-1.0,v1.12-debian-kinesis-1
docker-image/v1.12/debian-kinesis/Dockerfile
v1.12.0-debian-azureblob-arm64-1.1,v1.12-debian-azureblob-arm64-1
docker-image/v1.12/arm64/debian-azureblob/Dockerfilev1.12.0-debian-elasticsearch7-arm64-1.0,v1.12-debian-elasticsearch7-arm64-1,v1-debian-elasticsearch-arm64
docker-image/v1.12/arm64/debian-elasticsearch7/Dockerfilev1.12.0-debian-elasticsearch6-arm64-1.0,v1.12-debian-elasticsearch6-arm64-1
docker-image/v1.12/arm64/debian-elasticsearch6/Dockerfilev1.12.0-debian-loggly-arm64-1.0,v1.12-debian-loggly-arm64-1
docker-image/v1.12/arm64/debian-loggly/Dockerfilev1.12.0-debian-logentries-arm64-1.0,v1.12-debian-logentries-arm64-1
docker-image/v1.12/arm64/debian-logentries/Dockerfilev1.12.0-debian-cloudwatch-arm64-1.1,v1.12-debian-cloudwatch-arm64-1
docker-image/v1.12/arm64/debian-cloudwatch/Dockerfilev1.12.0-debian-stackdriver-arm64-1.0,v1.12-debian-stackdriver-arm64-1
docker-image/v1.12/arm64/debian-stackdriver/Dockerfilev1.12.0-debian-s3-arm64-1.0,v1.12-debian-s3-arm64-1
docker-image/v1.12/arm64/debian-s3/Dockerfilev1.12.0-debian-syslog-arm64-1.0,v1.12-debian-syslog-arm64-1
docker-image/v1.12/arm64/debian-syslog/Dockerfilev1.12.0-debian-forward-arm64-1.0,v1.12-debian-forward-arm64-1
docker-image/v1.12/arm64/debian-forward/Dockerfilev1.12.0-debian-gcs-arm64-1.0,v1.12-debian-gcs-arm64-1
docker-image/v1.12/arm64/debian-gcs/Dockerfilev1.12.0-debian-graylog-arm64-1.0,v1.12-debian-graylog-arm64-1
docker-image/v1.12/arm64/debian-graylog/Dockerfilev1.12.0-debian-papertrail-arm64-1.0,v1.12-debian-papertrail-arm64-1
docker-image/v1.12/arm64/debian-papertrail/Dockerfilev1.12.0-debian-logzio-arm64-1.0,v1.12-debian-logzio-arm64-1
docker-image/v1.12/arm64/debian-logzio/Dockerfilev1.12.0-debian-kafka-arm64-1.0,v1.12-debian-kafka-arm64-1
docker-image/v1.12/arm64/debian-kafka/Dockerfilev1.12.0-debian-kafka2-arm64-1.0,v1.12-debian-kafka2-arm64-1
docker-image/v1.12/arm64/debian-kafka2/Dockerfilev1.12.0-debian-kinesis-arm64-1.0,v1.12-debian-kinesis-arm64-1
docker-image/v1.12/arm64/debian-kinesis/Dockerfile
You can also use v1-debian-PLUGIN
tag to refer latest v1 image, e.g. v1-debian-elasticsearch
. On production, strict tag is better to avoid unexpected update.
See dockerhub's tags page for older tags.
v0.12 development has been ended. These images are never updated.
v0.12-debian-elasticsearch
docker-image/v0.12/debian-elasticsearch/Dockerfilev0.12-debian-loggly
docker-image/v0.12/debian-loggly/Dockerfilev0.12-debian-logentries
docker-image/v0.12/debian-logentries/Dockerfilev0.12-debian-cloudwatch
docker-image/v0.12/debian-cloudwatch/Dockerfilev0.12-debian-stackdriver
docker-image/v0.12/debian-stackdriver/Dockerfilev0.12-debian-s3
docker-image/v0.12/debian-s3/Dockerfilev0.12-debian-gcs
docker-image/v0.12/debian-gcs/Dockerfilev0.12-debian-papertrail
docker-image/v0.12/debian-papertrail/Dockerfilev0.12-debian-syslog
docker-image/v0.12/debian-syslog/Dockerfilev0.12-debian-graylog
docker-image/v0.12/debian-graylog/Dockerfilev0.12-debian-logzio
docker-image/v0.12/debian-logzio/Dockerfilev0.12-debian-kafka
docker-image/v0.12/debian-kafka/Dockerfilev0.12-debian-splunkhec
docker-image/v0.12/debian-splunkhec/Dockerfilev0.12-debian-kinesis
docker-image/v0.12/debian-kinesis/Dockerfile
v0.12-alpine-elasticsearch
docker-image/v0.12/alpine-elasticsearch/Dockerfilev0.12-alpine-loggly
docker-image/v0.12/alpine-loggly/Dockerfilev0.12-alpine-logentries
docker-image/v0.12/alpine-logentries/Dockerfilev0.12-alpine-cloudwatch
docker-image/v0.12/alpine-cloudwatch/Dockerfilev0.12-alpine-stackdriver
docker-image/v0.12/alpine-stackdriver/Dockerfilev0.12-alpine-s3
docker-image/v0.12/alpine-s3/Dockerfilev0.12-alpine-gcs
docker-image/v0.12/alpine-gcs/Dockerfilev0.12-alpine-papertrail
docker-image/v0.12/alpine-papertrail/Dockerfilev0.12-alpine-syslog
docker-image/v0.12/alpine-syslog/Dockerfilev0.12-alpine-graylog
docker-image/v0.12/alpine-graylog/Dockerfilev0.12-alpine-logzio
docker-image/v0.12/alpine-logzio/Dockerfilev0.12-alpine-kafka
docker-image/v0.12/alpine-kafka/Dockerfilev0.12-alpine-kinesis
docker-image/v0.12/alpine-kinesis/Dockerfilev0.12-alpine-splunkhec
docker-image/v0.12/alpine-splunkhec/Dockerfile
Fluentd is an open source data collector, which lets you unify the data collection and consumption for a better use and understanding of data.
Fluentd versioning is as follows:
Series | Description |
---|---|
v1.x | current stable |
v0.12 | Old stable, no longer updated |
Default YAML uses latest v1 images like fluent/fluentd-kubernetes-daemonset:v1-debian-kafka
. If you want to avoid unexpected image update, specify exact version for image
like fluent/fluentd-kubernetes-daemonset:v1.8.0-debian-kafka-1.0
.
This is for v0.12 images.
In Kubernetes and default setting, fluentd needs root permission to read logs in /var/log
and write pos_file
to /var/log
.
To avoid permission error, you need to set FLUENT_UID
environment variable to 0
in your Kubernetes configuration.
These images have default configuration and support some environment variables for parameters but it sometimes doesn't fit your case. If you want to use your configuration, use ConfigMap feature.
Each image has following configurations:
- fluent.conf: Destination setting, Elaticsearch, kafka and etc.
- kubernetes.conf: k8s specific setting.
tail
input for log files andkubernetes_metadata
filter - prometheus.conf: prometheus plugin for fluentd monitoring
- systemd.conf: systemd plugin for collecting systemd-journal log. See also "Disable systemd input" section.
Overwrite conf file via ConfigMap. See also several examples:
Since v1.9.3 or later images.
You can exclude container logs from /var/log/containers/
with FLUENT_CONTAINER_TAIL_EXCLUDE_PATH
.
If you have a trouble with specific log, use this envvar, e.g. ["/var/log/containers/logname-*"]
.
exclude_path
parameter document: https://docs.fluentd.org/input/tail#exclude_path- Fluentd log issue with backslash: fluent/fluentd#2545
If you don't setup systemd in the container, fluentd shows following messages by default configuration.
[warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s
[warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s
[warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s
You can suppress these messages by setting disable
to FLUENTD_SYSTEMD_CONF
environment variable in your kubernetes configuration.
By default, latest images launch prometheus
plugins to monitor fluentd.
You can disable prometheus input plugin by setting disable
to FLUENTD_PROMETHEUS_CONF
environment variable in your kubernetes configuration.
This is for older images. Latest elasticsearch images don't use sed.
By historical reason, elasaticsearch image executes sed
command during startup phase when FLUENT_ELASTICSEARCH_USER
or FLUENT_ELASTICSEARCH_PASSWORD
is specified. This sometimes causes a problem with read only mount.
To avoid this problem, set "true" to FLUENT_ELASTICSEARCH_SED_DISABLE
environment variable in your kubernetes configuration.
This daemonset setting mounts /var/log
as service account fluentd
so you need to run containers as privileged container.
Here is command example:
oc project kube-system
oc create -f https://raw.githubusercontent.com/fluent/fluentd-kubernetes-daemonset/master/fluentd-daemonset-elasticsearch-rbac.yaml
oc adm policy add-scc-to-user privileged -z fluentd
oc patch ds fluentd -p "spec:
template:
spec:
containers:
- name: fluentd
securityContext:
privileged: true"
oc delete pod -l k8s-app=fluentd-logging
This is from nekop's japanese article.
zookeeper gem doesn't work on Debian 10, so kafka image doesn't include zookeeper gem.
Maintainers don't have k8s experience on Windows. Some users create k8s daemonset on Windows:
Please check them out.
Using debian-kafka2/debian-kafka2-arm64 images are better than using debian-kafka/debian-kafka-arm64 images.
Because debian-kafka2/debian-kafka2-arm64 images use out_kafka2
plugin but debina-kafka/debian-kafka-arm64 images use deprecated out_kafka_buffered
plugin.
Some images are contributed by users. If you have a problem/question for following images, ask it to contributors.
- azureblob : @elsesiy
- papertrail : @alexouzounis
- kafka : @erhudy
- graylog : @rtnpro
- gcs : @andor-pierdelacabeza
- Amazon Kinesis : @shiftky
- logz.io : @SaMnCo / @jamielennox
- splunkhec: @FutureSharks
Currently, we don't accept new destination request without contribution. See fluent#293
Kubernetes Logging with Fluentd
We can't notice comments in the DockerHub so don't use them for reporting issues or asking question.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
Update templates
files instead of docker-image
files.
docker-image
files are automatically generated from templates
.
Note: This file is generated from templates/README.md.erb