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

<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: [January 6, 2019, 1:43pm UTC](https://meta.discourse.org/t/using-a-launcher-built-docker-image-in-docker-compose/105804/3 "2019-01-06T13:43:50Z")

</div>

G’day Jay

> [@pfaffman](#):
>
> If you use bitnami you will need to get support from them, and I’m pretty sure they provide none

I wasn’t asking for help with Bitnami … that was just background. It would be too different from the staging environments that uses .launcher.

I’m following the lead from [Can Discourse ship frequent Docker images that do not need to be bootstrapped? - #26 by sam](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205/26) which basically said using the output from .launcher is the way to go if you want to use docker-composer.

---

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