-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Windows) Metricbeat will not start due to config file permissions #76
Labels
Comments
@kaijunxu for the moment support on Windows for demo is not tested. |
i got same question!, when well fix ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 tocommand: -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.
The text was updated successfully, but these errors were encountered: