Fluentd is an open source data collector, which lets you unify the data collection and consumption for a better use and understanding of data. https://www.fluentd.org
$ docker run --name fluentd bitnami/fluentd:latest- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
- All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use
DOCKER_CONTENT_TRUST=1to verify the integrity of the images. - Bitnami container images are released daily with the latest distribution packages available.
This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
You can find an example for testing in the file test.yaml. To launch this sample file run:
$ kubectl apply -f test.yamlNOTE: If you are pulling from a private containers registry, replace the image name with the full URL to the docker image. E.g.
- image: 'your-registry/image-name:your-version'
NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
1-ol-7,1.8.0-ol-7-r6(1/ol-7/Dockerfile)1-debian-9,1.8.0-debian-9-r5,1,1.8.0,1.8.0-r5,latest(1/debian-9/Dockerfile)
Subscribe to project updates by watching the bitnami/fluentd GitHub repo.
The recommended way to get the Bitnami Fluentd Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/fluentd:latestTo use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
$ docker pull bitnami/fluentd:[TAG]If you wish, you can also build the image yourself.
$ docker build -t bitnami/fluentd:latest 'https://github.com/bitnami/bitnami-docker-fluentd.git#master:1/debian-9'Using Docker container networking, a different server running inside a container can easily be accessed by your application containers and vice-versa.
Containers attached to the same network can communicate with each other using the container name as the hostname.
$ docker network create fluentd-network --driver bridgeUse the --network <NETWORK> argument to the docker run command to attach the container to the fluentd-network network.
$ docker run --name fluentd-node1 --network fluentd-network bitnami/fluentd:latestWe can launch another containers using the same flag (--network NETWORK) in the docker run command. If you also set a name to your container, you will be able to use it as hostname in your network.
To create an endpoint that collects logs on your host just run:
docker run -d -p 24224:24224 -p 24224:24224/udp -v /data:/opt/bitnami/fluentd/log fluentd
Default configurations are:
- configuration file at
/opt/bitnami/fluentd/conf/fluentd.conf - listen port
24224for Fluentd forward protocol - store logs with tag
docker.**into/opt/bitnami/fluentd/log/docker.*.log - store all other logs into
/opt/bitnami/fluentd/log/data.*.log
You can overwrite the default configuration file by mounting your own configuration file on the directory /opt/bitnami/fluentd/conf:
docker run --name fluentd -v /path/to/fluentd.conf:/opt/bitnami/fluentd/conf/fluentd.conf bitnami/fluentd:latest
You can also do this by changing the docker-compose.yml file present in this repository:
fluentd:
...
volumes:
- /path/to/fluentd.conf:/opt/bitnami/fluentd/conf/fluentd.conf
...You can also extend the default configuration by importing your custom configuration with the "@include" directive. It is a simple as creating a directory with you custom config files and mount it on the directory /opt/bitnami/fluentd/conf/conf.d:
docker run --name fluentd -v /path/to/custom-conf-directory:/opt/bitnami/fluentd/conf/conf.d bitnami/fluentd:latest
You can also do this by changing the docker-compose.yml file present in this repository:
fluentd:
...
volumes:
- /path/to/custom-conf-directory:/opt/bitnami/fluentd/conf/conf.d
...Find more information about this feature, consult official documentation
Environment variable below are configurable to control how to execute fluentd process:
FLUENTD_CONF: 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).FLUENTD_OPT: Use this variable to specify other Fluentd command line options, like -v or -q.FLUENTD_DAEMON_USER: The user that will run thefluentdprocess when the container is run as root.FLUENTD_DAEMON_GROUP: The group of the user that will run thefluentdprocess when the container is run as root.
The Bitnami fluentd Docker image sends the container logs to the stdout. To view the logs:
$ docker logs fluentdYou can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.
Bitnami provides up-to-date versions of fluentd, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
$ docker pull bitnami/fluentd:latestStop the currently running container using the command
$ docker stop fluentdNext, take a snapshot of the persistent volume /path/to/fluentd-persistence using:
$ rsync -a /path/to/fluentd-persistence /path/to/fluentd-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)You can use this snapshot to restore the database state should the upgrade fail.
$ docker rm -v fluentdRe-create your container from the new image, restoring your backup if necessary.
$ docker run --name fluentd bitnami/fluentd:latestWe'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version) - Output of
docker info - Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright (c) 2019 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.