# فشل التمهيد \[نظام الملفات للقراءة فقط\]

**URL:** <https://meta.discourse.org/t/failed-to-bootstrap-read-only-filesystem/115088>\
**Category:** Product Support\
**Created:** [15 أبريل 2019، 10:34ص UTC](https://meta.discourse.org/t/failed-to-bootstrap-read-only-filesystem/115088 "2019-04-15T10:34:44Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![schleifer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schleifer/32/86416_2.png) [@schleifer](https://meta.discourse.org/u/schleifer)\
**Post date:** [15 أبريل 2019، 1:49م UTC](https://meta.discourse.org/t/failed-to-bootstrap-read-only-filesystem/115088/7 "2019-04-15T13:49:56Z")

</div>

> [@c0ry](#):
>
> /usr/bin/docker: Error response from daemon: error while creating mount source path ‘/var/discourse/shared/standalone’: mkdir /var/discourse: read-only file system.

This error message is completely unrelated to changing ports. The filesystem has gone read-only for some reason and the docker daemon cannot start the container. You need to figure out why it’s read-only.

---

_[View the full topic](https://meta.discourse.org/t/failed-to-bootstrap-read-only-filesystem/115088)._
