# Fail to run directly docker-compose from /discourse-docker/image/base on Windows in Virtual Machine

**URL:** https://meta.discourse.org/t/fail-to-run-directly-docker-compose-from-discourse-docker-image-base-on-windows-in-virtual-machine/99443
**Category:** Self-hosting
**Created:** [October 13, 2018, 7:11pm UTC](https://meta.discourse.org/t/fail-to-run-directly-docker-compose-from-discourse-docker-image-base-on-windows-in-virtual-machine/99443 "2018-10-13T19:11:45Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [October 14, 2018, 3:58pm UTC](https://meta.discourse.org/t/fail-to-run-directly-docker-compose-from-discourse-docker-image-base-on-windows-in-virtual-machine/99443/5 "2018-10-14T15:58:09Z")

</div>

You will need to use launcher, push the resulting image to a Docker registry, and then use this image in the docker compose.

You can read more about this in [Can Discourse ship frequent Docker images that do not need to be bootstrapped?](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205)

---

_[View the full topic](https://meta.discourse.org/t/fail-to-run-directly-docker-compose-from-discourse-docker-image-base-on-windows-in-virtual-machine/99443)._
