Looking at the Logstash docker images, I went ahead and created a custom image, including base .net framework and adding the logstash installation folder to it, by virtue of downloading the zip file, extracting it and customizing the yml, conf files as required.
All of this works fine, when building the docker image. When running the docker image - creating container - logstash doesn't start off from the powershell by using cmd /c "C:/logstash-7.12.0/bin/logstash -f logstash.conf",
where C:\logstash-7.12.0 is where logstash is getting installed on the container and logstash.conf (with input-beats=> port 5044, output - kusto) is configured and kept in the bin folder itself.
After trying to run the docker image, logstash-output-kusto gets installed fine, but after that logstash is unable to run using the logstash -f command specified above.
No error nothing, but the process seems to get hung after these messages below -
Starting Logstash
Using JAVA_HOME defined java: C:\logstash-7.12.0\jdk
WARNING, using JAVA_HOME while Logstash distribution comes with a bundled JDK
Unable to get Charset 'cp0' for property 'sun.stdout.encoding', using default UTF-8 and
continuing.
Sending Logstash logs to C:/logstash-7.12.0/logs which is now configured via log4j2.properties
Unable to get Charset 'cp0' for property 'sun.stdout.encoding', using default UTF-8 and
continuing.
Unable to get Charset 'cp0' for property 'sun.stdout.encoding', using default UTF-8 and
continuing.
Unable to get Charset 'cp0' for property 'sun.stdout.encoding', using default UTF-8 and
continuing.
Unable to get Charset 'cp0' for property 'sun.stdout.encoding', using default UTF-8 and
continuing.
**[2021-04-21T09:23:02,741][WARN ][logstash.config.source.multilocal] Ignoring the **
** 'pipelines.yml' file because modules or command line options are specified**