# 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:** [7 Septiembre, 2014 07: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:** 8

<div class="post-metadata">

**Author:** ![maze](https://avatars.discourse-cdn.com/v4/letter/m/e9a140/32.png) [@maze](https://meta.discourse.org/u/maze)\
**Post date:** [10 Septiembre, 2014 07:48 UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745/8 "2014-09-10T07:48:45Z")

</div>

> [@codinghorror](#):
>
> I am curious if that 40% less memory figure is true! has anyone compared a 1GB DO Ubuntu image with Discourse, to a 1GB DO CoreOS image?

On a 1 GB CoreOS machine without swap, I had to cut down the number of unicorn instances to two. Also the update function (at `/admin/upgrade`) leads to out-of-memory situations. I have to stop the unicorns before trying to do that.

---

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