-e doesn't work using logstash image from docker.elastic.co

Elastic Stack Logstash
1

I'm trying to switch from the logstash official image on Docker Hub to Elastic's registry, given the Docker Hub images won't be updated past June 20. But, the image provided by Elastic's registry doesn't seem to work properly. The following command produces an error using Elastic's image, as opposed to the image published in Docker Hub.

(rmsdev) →  ✗ docker run -it --rm docker.elastic.co/logstash/logstash:5.4.0 -e 'input { stdin { } } output { stdout { } }'
ERROR: Unknown command '{'

See: 'bin/logstash --help'

Any ideas why?

2

It is a known issue. We will fix it soon.

3

Hi!

Thanks for reporting this. It was caused by some sloppy shell scripting (by me) that wasn't handling whitespace correctly.

It's now fixed by this patch and a new image for version 5.4.0 has been pushed.