# Native Scheduler: Docker Read-only Container Filesystem

**URL:** <https://community.replicated.com/t/native-scheduler-docker-read-only-container-filesystem/1120>\
**Category:** Uncategorized\
**Created:** [February 6, 2023, 5:50pm UTC](https://community.replicated.com/t/native-scheduler-docker-read-only-container-filesystem/1120 "2023-02-06T17:50:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dex](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dex/32/26_2.png) [@dex](https://community.replicated.com/u/dex)\
**Post date:** [February 6, 2023, 5:50pm UTC](https://community.replicated.com/t/native-scheduler-docker-read-only-container-filesystem/1120/1 "2023-02-06T17:50:46Z")

</div>

I know mounted volumes can be mounted with flags like `ro`, per [Container Volumes](https://help.replicated.com/docs/native/packaging-an-application/volumes/), but is there a way to ensure the container’s entire internal root filesystem is mounted as read-only? Is there any workaround to do this via a Dockerfile directive?

---

<div class="post-metadata">

**Author:** ![dmitriy](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dmitriy/32/16_2.png) [@dmitriy](https://community.replicated.com/u/dmitriy)\
**Post date:** [February 6, 2023, 6:20pm UTC](https://community.replicated.com/t/native-scheduler-docker-read-only-container-filesystem/1120/2 "2023-02-06T18:20:20Z")

</div>

There is not, as far I know. The only way to make the filesystem read-only is at run time, and that option is not supported via Replicated spec.