# Why elk requires a privilege container permission in Openshift

**URL:** <https://discuss.elastic.co/t/why-elk-requires-a-privilege-container-permission-in-openshift/264923>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [February 19, 2021, 11:26pm UTC](https://discuss.elastic.co/t/why-elk-requires-a-privilege-container-permission-in-openshift/264923 "2021-02-19T23:26:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roberto\_Ramirez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roberto_ramirez/32/84228_2.png) [@Roberto\_Ramirez](https://discuss.elastic.co/u/Roberto_Ramirez)\
**Post date:** [February 19, 2021, 11:26pm UTC](https://discuss.elastic.co/t/why-elk-requires-a-privilege-container-permission-in-openshift/264923/1 "2021-02-19T23:26:14Z")

</div>

I am trying to deploy elk in openshift 4.6 and i am getting the following error

create Pod elksaastest-master-0 in StatefulSet elktest-master failed error: pods elkstest-master-0 is forbidden: unable to validate against any security context constraint fsGroup Invalid value int641000 1000 is not an allowed group Privileged containers are not allowed

This is resolved adding the default service account of the project to the privileged SCC but I would like to know why elk requires the privilege container I need a justification for my Openshift administrator

---

<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:** [March 19, 2021, 11:26pm UTC](https://discuss.elastic.co/t/why-elk-requires-a-privilege-container-permission-in-openshift/264923/2 "2021-03-19T23:26:47Z")

</div>

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