# 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:** 5

<div class="post-metadata">

**Author:** ![julsevern](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/julsevern/32/103319_2.png) [@julsevern](https://meta.discourse.org/u/julsevern)\
**Post date:** [2014 年 9 月 8 日午後 4:37 UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745/5 "2014-09-08T16:37:11Z")

</div>

Ha yes, it cannot reduce memory usage magically 🙂 and the OS doesn’t have build and scripting tools whatsoever. The promised 40% is about the default not loaded OS footprint.

I had to increase the coreos KVM instance’s memory allocation from 1G, because of OOM errors in Discourse. However, it’s a good idea to run multiple dockers on the same image, for better memory utilization.

The other question is how we can leverage CoreOS’ cluster feature. The [documentation](https://coreos.com/docs/launching-containers/launching/launching-containers-fleet/) usually refers to a kill - rm - pull - run sequence, while `discourse_docker` keeps the original container if available. Is there a technology which updates the docker image other than `launcher rebuild`?

---

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