# Discourse in a Docker container

**URL:** <https://meta.discourse.org/t/discourse-in-a-docker-container/10844>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [8 בנובמבר,‏ 2013,‏ 12:12am UTC](https://meta.discourse.org/t/discourse-in-a-docker-container/10844 "2013-11-08T00:12:22Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![meglio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/meglio/32/71444_2.png) [@meglio](https://meta.discourse.org/u/meglio)\
**Post date:** [11 בינואר,‏ 2014,‏ 1:56am UTC](https://meta.discourse.org/t/discourse-in-a-docker-container/10844/7 "2014-01-11T01:56:45Z")

</div>

Just as a note, I’ve tried **Docker** #1 (i.e. **Sam’s GitHub readme file** ) on top of a **fresh $5 DigitalOcean VPS** (the smallest one). Watching htop: ~80% of the time my CPU is 100% busy with sidekiq, memory usage 450MB out of 490MB. Is this because of Docker or just because of the nature of the environment Discourse is built on? (i.e. ruby, so there is just some minimal requirement that should be _always_ met no matter whether any kind of virtualization is used or not).

---

_[View the full topic](https://meta.discourse.org/t/discourse-in-a-docker-container/10844)._