1.5.6-1,1.5.6,1.5,1(1.5/Dockerfile)2.0.0-1,2.0.0,2.0(2.0/Dockerfile)2.1.3-1,2.1.3,2.1(2.1/Dockerfile)2.2.4-1,2.2.4,2.2(2.2/Dockerfile)2.3.4-1,2.3.4,2.3,2,latest(2.3/Dockerfile)5.0.0-alpha4-1,5.0.0-alpha4,5.0.0,5.0,5(5.0/Dockerfile)
For more information about this image and its history, please see the relevant manifest file (library/logstash). This image is updated via pull requests to the docker-library/official-images GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the logstash/tag-details.md file in the docker-library/docs GitHub repo.
Logstash is a tool that can be used to collect, process and forward events and log messages. Collection is accomplished via number of configurable input plugins including raw socket/packet communication, file tailing and several message bus clients. Once an input plugin has collected data it can be processed by any number of filters which modify and annotate the event data. Finally events are routed to output plugins which can forward the events to a variety of external programs including Elasticsearch, local files and several message bus implementations.
If you need to run logstash with configuration provided on the commandline, you can use the logstash image as follows:
$ docker run -it --rm logstash logstash -e 'input { stdin { } } output { stdout { } }'If you need to run logstash with a configuration file, logstash.conf, that's located in your current directory, you can use the logstash image as follows:
$ docker run -it --rm -v "$PWD":/config-dir logstash logstash -f /config-dir/logstash.confView license information for the software contained in this image.
This image is officially supported on Docker version 1.12.0.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the logstash/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.
You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.