# 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:** [January 6, 2019, 12:15pm 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:** 17

<div class="post-metadata">

### Author: ![csmu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/csmu/32/124581_2.png) [@csmu](https://meta.discourse.org/u/csmu)
#### Post date: [August 31, 2019, 5:41am UTC](https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804/17 "2019-08-31T05:41:21Z")

</div>

> [@dnk8n](#):
>
> Maybe the open-sourced supported version is purposefully not orchestration manager friendly so that they can get contracts to manage deploys that require massive scale.

My understanding is it for ease of support - that CDKC uses the open sourced version - they do make their income from hosting and that pays for the free support they give to the official supported version.

There is a guide to splitting the containers here [Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084)

We did manage to get a instance running under docker-compose so what you’re aiming for is certainly doable.

---

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