# CentOS 6.6, no docker upgrade supported, hence no discourse rebuild

**URL:** <https://meta.discourse.org/t/centos-6-6-no-docker-upgrade-supported-hence-no-discourse-rebuild/47070>\
**Category:** Product Support\
**Created:** [2016 年 7 月 11 日午前 6:28 UTC](https://meta.discourse.org/t/centos-6-6-no-docker-upgrade-supported-hence-no-discourse-rebuild/47070 "2016-07-11T06:28:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [2016 年 7 月 12 日午前 7:51 UTC](https://meta.discourse.org/t/centos-6-6-no-docker-upgrade-supported-hence-no-discourse-rebuild/47070/6 "2016-07-12T07:51:48Z")

</div>

> [@Himanshu\_Chhangani](#):
>
> as if like copying all the contents of /var/discourse to other instance ?

Yes, as the database lives in this directory as well. After confirming that the container is stopped, simply copying all of this (including the container definitions and the `shared` directory) should allow you to rebuild on a different machine.

---

_[View the full topic](https://meta.discourse.org/t/centos-6-6-no-docker-upgrade-supported-hence-no-discourse-rebuild/47070)._