# 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:** [Setembro 7, 2014, 7:59am 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:** 2

<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:** [Setembro 7, 2014, 8:05am UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745/2 "2014-09-07T08:05:20Z")

</div>

Interesting

> **[Red Hat OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)**
>
> A unified application development platform that lets you build, modernize, and deploy applications at scale on your choice of hybrid cloud infrastructure.

- claims 40% less memory use
- automatic full OS update scheme
- native / required Docker image support for all software installs
- optimized for large “cloud” provisioning of many servers
- read only OS images

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?

---

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