[root@VM_0_6_centos pipeline]# cat logstash.yml

#http.host: "0.0.0.0"

#xpack.monitoring.elasticsearch.url: http://10.0.0.92:9200

可以定义成空，会有一下warn告警

 docker run --rm -it    -v /tmp/pipeline/messages:/usr/share/logstash/config/messages -v /tmp/pipeline/test.conf:

/usr/share/logstash/pipeline/test.conf -v /tmp/pipeline/logstash.yml:/usr/share/logstash/config/logstash.yml docker.elastic.co/logstash/logstash

:6.4.

bash-4.2$ cat /usr/share/logstash/config/pipelines.yml

- pipeline.id: main

  path.config: "/usr/share/logstash/pipeline"

cd /usr/share/logstash/pipeline
#################################/usr/share/logstash/pipeline

[root@VM_0_6_centos pipeline]# cat test.conf

input {

    file {

        path => ["/usr/share/logstash/config/messages"]

        type => "nodelog"

    }

}

filter {

}

output {

    elasticsearch {

          hosts => ["10.0.0.92:9200"]

          index => "nodelog-%{+YYY.MM.dd}"

    }

    stdout {

codec => rubydebug

    }

}

Bind-mounted configuration files will retain the same permissions and ownership within the container that they have on the
 host system. Be sure to set permissions such that the files will be readable and, ideally, 
not writeable by the container’s logstash user (UID ).