# Report on using discourse\_docker on a CoreOS image

**URL:** <https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [2014 年 9 月 7 日午前 7:59 UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745 "2014-09-07T07:59:26Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2014 年 9 月 10 日午前 7:51 UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745/9 "2014-09-10T07:51:47Z")

</div>

That’s the same as it is on Ubuntu. We recommend only 2 workers on 1GB per the [official install](https://meta.discourse.org/t/142537?silent=true) docs, and we also recommend setting up swap to cover the upgrade case – upgrading chews through a ton of memory.

---

_[View the full topic](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745)._