# Elasticsearch 7.17.7 ReadOnly Root FileSystem/Privileged Container

**URL:** <https://discuss.elastic.co/t/elasticsearch-7-17-7-readonly-root-filesystem-privileged-container/319473>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [November 21, 2022, 3:37pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-7-readonly-root-filesystem-privileged-container/319473 "2022-11-21T15:37:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsoares82](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@rsoares82](https://discuss.elastic.co/u/rsoares82)\
**Post date:** [November 21, 2022, 3:37pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-7-readonly-root-filesystem-privileged-container/319473/1 "2022-11-21T15:37:23Z")

</div>

Hi all,

I am using elasticsearch on version 7.17.7 we deploy to kubernetes using helm charts, it happens that our containers are marked vulnerable because they don't have a read only root file system and the containers are privileged. The main thing is the sysctl container that need this type of permissions in order to be able to initialize the other containers and set the vm.max\_map\_count.

my questions are:  
can I do this in any other way without having a privileged container?  
can I set a readonly root file system for elasticsearch?

if yes, how?

Thanks for the help

---

<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:** [December 19, 2022, 3:38pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-7-readonly-root-filesystem-privileged-container/319473/2 "2022-12-19T15:38:04Z")

</div>

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