# Filebeat configuration file permission **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [October 11, 2018, 1:54pm UTC](https://discuss.elastic.co/t/filebeat-configuration-file-permission/152063 "2018-10-11T13:54:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sumitdatta](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@sumitdatta](https://discuss.elastic.co/u/sumitdatta)\ **Post date:** [October 11, 2018, 1:54pm UTC](https://discuss.elastic.co/t/filebeat-configuration-file-permission/152063/1 "2018-10-11T13:54:55Z")
Hi all, We are trying to configure filebeat to our openshift cluster. Filebeat configuration file will be directly taken from openshift persistence volume at the time of container creation and we don't have root privilege in our system. while creating the container its failing with this exception(Exiting: error loading config file: config file ("/usr/share/filebeat/filebeat.yml") must be owned by the beat user (uid=0) or root). Please help us to resolve this incidence. ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [October 12, 2018, 11:49pm UTC](https://discuss.elastic.co/t/filebeat-configuration-file-permission/152063/2 "2018-10-12T23:49:38Z")
As filebeat is run as root, it's a potential security issue that the config file is owned or editable by other users. You can disable the check by adding the command line flag `--strict.perms false` when starting filebeat. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 9, 2018, 11:49pm UTC](https://discuss.elastic.co/t/filebeat-configuration-file-permission/152063/3 "2018-11-09T23:49:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.