# Using a launcher built docker image in docker-compose

**URL:** https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804
**Category:** Development
**Created:** [1월 6, 2019, 12:15오후 UTC](https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804 "2019-01-06T12:15:33Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [1월 6, 2019, 10:42오후 UTC](https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804/9 "2019-01-06T22:42:40Z")

</div>

I am super confused at why you would even want to involve compose.

This gives your devs an ultra easy setup path on local:

> [@Install Discourse for development using Docker](https://meta.discourse.org/t/beginners-guide-to-install-discourse-for-development-using-docker/102009):
>
> Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development container. white_check_mark Pros: No need to install any system dependencies, no configuration needed at all for setting up a development environment quickly. x Cons: Will be slightly slower than the native dev environment on Ubuntu, and much slower than a native install on MacOS. See also [Developing Discourse using a Dev Container](https://meta.discourse.org/t/developing-discourse-using-a-dev-container/336366) …

In production … why would you even think about deploying with compose? In general production container orchestration happens in either scripts or kubernates or some other dedicated production tool.

---

_[View the full topic](https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804)._