See also dockerhub tags page: https://hub.docker.com/r/fluent/fluentd-kubernetes-daemonset/tags
v1.7.0-debian-elasticsearch7-1.1,v1.7-debian-elasticsearch7-1,v1-debian-elasticsearchdocker-image/v1.7/debian-elasticsearch7/Dockerfilev1.7.0-debian-elasticsearch6-1.1,v1.7-debian-elasticsearch6-1docker-image/v1.7/debian-elasticsearch6/Dockerfilev1.7.0-debian-loggly-1.1,v1.7-debian-loggly-1docker-image/v1.7/debian-loggly/Dockerfilev1.7.0-debian-logentries-1.1,v1.7-debian-logentries-1docker-image/v1.7/debian-logentries/Dockerfilev1.7.0-debian-cloudwatch-1.1,v1.7-debian-cloudwatch-1docker-image/v1.7/debian-cloudwatch/Dockerfilev1.7.0-debian-stackdriver-1.1,v1.7-debian-stackdriver-1docker-image/v1.7/debian-stackdriver/Dockerfilev1.7.0-debian-s3-1.1,v1.7-debian-s3-1docker-image/v1.7/debian-s3/Dockerfilev1.7.0-debian-syslog-1.1,v1.7-debian-syslog-1docker-image/v1.7/debian-syslog/Dockerfilev1.7.0-debian-forward-1.1,v1.7-debian-forward-1docker-image/v1.7/debian-forward/Dockerfilev1.7.0-debian-gcs-1.1,v1.7-debian-gcs-1docker-image/v1.7/debian-gcs/Dockerfilev1.7.0-debian-graylog-1.1,v1.7-debian-graylog-1docker-image/v1.7/debian-graylog/Dockerfilev1.7.0-debian-papertrail-1.1,v1.7-debian-papertrail-1docker-image/v1.7/debian-papertrail/Dockerfilev1.7.0-debian-logzio-1.1,v1.7-debian-logzio-1docker-image/v1.7/debian-logzio/Dockerfilev1.7.0-debian-kafka-1.1,v1.7-debian-kafka-1docker-image/v1.7/debian-kafka/Dockerfilev1.7.0-debian-kinesis-1.1,v1.7-debian-kinesis-1docker-image/v1.7/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-debian-elasticsearchdocker-image/v0.12/debian-elasticsearch/Dockerfilev0.12-debian-logglydocker-image/v0.12/debian-loggly/Dockerfilev0.12-debian-logentriesdocker-image/v0.12/debian-logentries/Dockerfilev0.12-debian-cloudwatchdocker-image/v0.12/debian-cloudwatch/Dockerfilev0.12-debian-stackdriverdocker-image/v0.12/debian-stackdriver/Dockerfilev0.12-debian-s3docker-image/v0.12/debian-s3/Dockerfilev0.12-debian-gcsdocker-image/v0.12/debian-gcs/Dockerfilev0.12-debian-papertraildocker-image/v0.12/debian-papertrail/Dockerfilev0.12-debian-syslogdocker-image/v0.12/debian-syslog/Dockerfilev0.12-debian-graylogdocker-image/v0.12/debian-graylog/Dockerfilev0.12-debian-logziodocker-image/v0.12/debian-logzio/Dockerfilev0.12-debian-kafkadocker-image/v0.12/debian-kafka/Dockerfilev0.12-debian-splunkhecdocker-image/v0.12/debian-splunkhec/Dockerfilev0.12-debian-kinesisdocker-image/v0.12/debian-kinesis/Dockerfile
v0.12-alpine-elasticsearchdocker-image/v0.12/alpine-elasticsearch/Dockerfilev0.12-alpine-logglydocker-image/v0.12/alpine-loggly/Dockerfilev0.12-alpine-logentriesdocker-image/v0.12/alpine-logentries/Dockerfilev0.12-alpine-cloudwatchdocker-image/v0.12/alpine-cloudwatch/Dockerfilev0.12-alpine-stackdriverdocker-image/v0.12/alpine-stackdriver/Dockerfilev0.12-alpine-s3docker-image/v0.12/alpine-s3/Dockerfilev0.12-alpine-gcsdocker-image/v0.12/alpine-gcs/Dockerfilev0.12-alpine-papertraildocker-image/v0.12/alpine-papertrail/Dockerfilev0.12-alpine-syslogdocker-image/v0.12/alpine-syslog/Dockerfilev0.12-alpine-graylogdocker-image/v0.12/alpine-graylog/Dockerfilev0.12-alpine-logziodocker-image/v0.12/alpine-logzio/Dockerfilev0.12-alpine-kafkadocker-image/v0.12/alpine-kafka/Dockerfilev0.12-alpine-kinesisdocker-image/v0.12/alpine-kinesis/Dockerfilev0.12-alpine-splunkhecdocker-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 |
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.
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.
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.
Some images are contributed by users. If you have a problem/question for following images, ask it to contributors.
- cloudwatch : @so0k
- papertrail : @alexouzounis
- kafka : @erhudy
- graylog : @rtnpro
- gcs : @andor-pierdelacabeza
- Amazon Kinesis : @shiftky
- logz.io : @SaMnCo / @jamielennox
- splunkhec: @FutureSharks
Kubernetes Logging with Fluentd
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.
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.
Note: This file is generated from templates/README.md.erb