# Install Discourse for development using Docker

**URL:** https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009
**Category:** Developer Guides
**Tags:** docker, dev-install, how-to
**Created:** [November 16, 2018, 9:40am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009 "2018-11-16T09:40:04Z")
**Posts on this page:** 1
**Showing post:** 94

<div class="post-metadata">

### Author: ![seanblue](https://avatars.discourse-cdn.com/v4/letter/s/dc4da7/32.png) [@seanblue](https://meta.discourse.org/u/seanblue)
#### Post date: [February 3, 2020, 4:38am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/94 "2020-02-03T04:38:03Z")

</div>

@sam Is what I’m trying to do even a remotely supported way of running Discourse for development? In the [Windows development thread](https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-windows-10-for-development/75149/49) you mentioned trying this, but it hasn’t been going great so far. Basic (non-Discourse) Ubuntu containers technically work, but not the specific commands in this thread’s OP.

You originally mentioned this to me:

> [@Install Discourse on Windows for development](https://meta.discourse.org/t/install-discourse-on-windows-for-development/75149/47):
>
> If you are feeling brave and are comfortable selecting the slow ring for insider builds I think WSL2 can work alright.
> 
> If not I would recommend traditional VM + docker for the easy path cause you will have more tooling.
> 
> Pure docker should work but leaves you with less flexibility.

So unless you have a suggestion to get me through the issues I’m having with Docker on Windows, it’s probably best for me to cut my losses and run it in an Ubuntu VM using something like Virtual Box.

---

_[View the full topic](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009)._
