# Install issues when not root

**URL:** <https://meta.discourse.org/t/install-issues-when-not-root/16538>\
**Category:** Self-hosting\
**Created:** [June 14, 2014, 1:13pm UTC](https://meta.discourse.org/t/install-issues-when-not-root/16538 "2014-06-14T13:13:06Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![thornburg](https://avatars.discourse-cdn.com/v4/letter/t/9fc348/32.png) [@thornburg](https://meta.discourse.org/u/thornburg)\
**Post date:** [June 25, 2014, 10:40pm UTC](https://meta.discourse.org/t/install-issues-when-not-root/16538/17 "2014-06-25T22:40:21Z")

</div>

> [@codinghorror](#):
>
> One thing that can cause Postgres database corruption is if somehow multiple Docker containers are trying to write to the database at the same time – remember that the database (and file uploads) are outside the Docker container, that’s why destroying and rebuilding containers doesn’t lose anything.

Discourse is the only container I have. I never used Docker before installing Discourse. I’ve never had two containers at the same time.

Nothing outside of Discourse uses Postgres.

Actually, my machine is currently reporting that Postgres isn’t even installed, which seems impossible, since I can still see all the posts/etc that were made before Discourse broke.

Or does the Postgres instance live entirely inside the container, invisible to the host machine?

EDIT: Postgres is listening on a few ports, so it’s clearly installed and running, whatever apt may tell me.

---

_[View the full topic](https://meta.discourse.org/t/install-issues-when-not-root/16538)._
