(Windows) Metricbeat will not start due to config file permissions

[kaijunxu]

When running on WSL2 on Windows, Metricbeat container will not start with error Exiting: error loading config file: config file ("metricbeat.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/metricbeat/metricbeat.yml') and end up in a restart loop. This may be related to known issues with file permissions on WSL/WSL2. This results in the Kibana dashboards showing "no data available".

Per Elastic documentation, this can be easily worked around by using the --strict.perms=false - for example modifying the docker-compose-override.yml file to command: -e --strict.perms=false. This is not a recommended fix but should be sufficient for demo and learning purposes.

Tested with 6.1.0-post, Ubuntu 18.04 on WSL2 (Windows 10). I suspect (but not tested) 6.2.0-post will have same issue. Impact for non-Windows users (e.g. Mac) not tested but I believe there will not be any impact from this change.

Recognize that we do not officially test these examples for Windows users, but this is a relatively simple workaround.

[hifly81]

@kaijunxu for the moment support on Windows for demo is not tested. Feel free to open a new issue to ask for demo support on Windows

[wensenz]

i got same question!, when well fix ?

[ejentos]

Guys as a workaround you can try to set 'read only' attribute to metricbeat.yml file. The problem should gone.

[hifly81]

@kaijunxu @wensenz are you happy with the workaround proposed by @ejentos ?