logstash

Utils

docker pull reg.mini.dev/logstash

Utils

Updated 1 hour ago

docker pull reg.mini.dev/logstash

Logstash Overview

Secure your stack with a hardened Logstash image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Logstash is a server-side data processing pipeline that ingests, transforms and sends data to analytics engines. Logstash is often used along with Elasticsearch and Kibana as part of the ELK stack for analyzing and visualizing log and event data in real time.

Try It Out

Create a configuration file logstash.conf with the input and output instructions:

input {
  file {
    path => "/usr/share/logstash/test.log"
    start_position => "beginning"
    sincedb_path => "/dev/null" 
  }
}

output {
  stdout {
    codec => rubydebug
  }
}

Create test.log file:

echo "Hello from Logstash!" > test.log

Run the Logstash container and mount the files you just created:

docker run --rm -it \
  -v $(pwd)/test.log:/usr/share/logstash/test.log \
  -v $(pwd)/logstash.conf:/usr/share/logstash/pipeline/logstash.conf \
  reg.mini.dev/logstash

Wait a minute for the image to start. It should print a message like this to your terminal:

{
    "@timestamp" => 2025-09-17T14:39:31.611121217Z,
         "event" => {
        "original" => "Hello from Logstash!"
    },
           "log" => {
        "file" => {
            "path" => "/usr/share/logstash/test.log"
        }
    },
       "message" => "Hello from Logstash!",
          "host" => {
        "name" => "b5a0d7db9c07"
    },
      "@version" => "1"
}

Deploy via a Helm chart

Logstash can be deployed via Helm as part of the Elastic Stack and managed by the ECK Operator. See the related charts tab to get started.

Technical Considerations

The Logstash image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Logstash built by Minimus:

Listens on but does not expose the default ports: 5044/tcp and 9600/tcp. The public image exposes the same ports by default.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.