# Install Discourse on an isolated CentOS 7 server

**URL:** https://meta.discourse.org/t/install-discourse-on-an-isolated-centos-7-server/73538
**Category:** Sysadmins
**Tags:** how-to, install
**Created:** [11월 6, 2017, 5:16오후 UTC](https://meta.discourse.org/t/install-discourse-on-an-isolated-centos-7-server/73538 "2017-11-06T17:16:03Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![nil4](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nil4/32/81796_2.png) [@nil4](https://meta.discourse.org/u/nil4)
#### Post date: [11월 7, 2017, 9:24오전 UTC](https://meta.discourse.org/t/install-discourse-on-an-isolated-centos-7-server/73538/3 "2017-11-07T09:24:58Z")

</div>

Unfortunately that did not work for me. The container Discourse runs in is not isolated from its host; the database, uploads, backups, etc. are stored in volumes mapped to the host file system. You need to copy those as well, and when I copied the bootstrapped container from another machine, I could not line up the file permissions between the users inside the container and those on the host.

See also the comments in the related thread [Discourse in a closed intranet](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449)

Another issue is that the launcher script does upgrades (Postgress DB migrations, for example) when time comes to update the Discourse version.

With this approach, I can simply update the local copies of Git repos and base Docker images, then run `./launcher rebuild app` and let it handle the upgrade correctly.

---

_[View the full topic](https://meta.discourse.org/t/install-discourse-on-an-isolated-centos-7-server/73538)._