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

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [May 21, 2021, 3:51pm UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/165 "2021-05-21T15:51:52Z")

</div>

> [@juli](#):
>
> If anyone is able to run Discourse using docker in a M1 Mac

I tried this today, and also ran into issues. The error I saw was because Docker’s architecture emulation doesn’t support `inotify` (which we use a lot in Discourse development). For now, I’ve added a warning to `d/boot_dev` when a non-x86\_64 architecture is detected:

```plaintext
❯ d/boot_dev 
WARNING: Docker architecture is not x86_64.
Discourse development is unlikely to work using Docker's architecture emulation.
Please try a native development installation.

```

> [@hawm](#):
>
> Hi, i think we should make a description about the Ember-CLI here

I’ve now added a `d/ember-cli` helper, and forwarded port 4200 by default. The info at the top of this topis has also been updated. Once you’ve updated, run `d/rails s` in one terminal, and `d/ember-cli` in another. I’ve also set `NO_EMBER_CLI` as one of the variables which is passed through to Docker, so that is available if needed.

---

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