# Running filebeat as non-root in Kubernetes?

**URL:** <https://discuss.elastic.co/t/running-filebeat-as-non-root-in-kubernetes/176652>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 12, 2019, 3:01pm UTC](https://discuss.elastic.co/t/running-filebeat-as-non-root-in-kubernetes/176652 "2019-04-12T15:01:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vincehood](https://avatars.discourse-cdn.com/v4/letter/v/90ced4/32.png) [@Vincehood](https://discuss.elastic.co/u/Vincehood)\
**Post date:** [April 12, 2019, 3:01pm UTC](https://discuss.elastic.co/t/running-filebeat-as-non-root-in-kubernetes/176652/1 "2019-04-12T15:01:25Z")

</div>

Hi,  
the filebeat Helm chart ([https://raw.githubusercontent.com/elastic/beats/7.0/deploy/kubernetes/filebeat-kubernetes.yaml](https://raw.githubusercontent.com/elastic/beats/7.0/deploy/kubernetes/filebeat-kubernetes.yaml)) specifies that the user shall be root (runAsUser: 0).  
Is there any other way to achieve application container logging with the Elastic stack that does not rely on running filebeat as root?  
Can filebeat be run as non-root to achieve logging?  
Br  
/Vincehood

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 10, 2019, 3:01pm UTC](https://discuss.elastic.co/t/running-filebeat-as-non-root-in-kubernetes/176652/2 "2019-05-10T15:01:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.