# Docker setup for development

**URL:** <https://meta.discourse.org/t/docker-setup-for-development/72354>\
**Category:** Development\
**Created:** [18 أكتوبر 2017، 5:02م UTC](https://meta.discourse.org/t/docker-setup-for-development/72354 "2017-10-18T17:02:25Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![xrav3nz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/xrav3nz/32/76894_2.png) [@xrav3nz](https://meta.discourse.org/u/xrav3nz)\
**Post date:** [18 أكتوبر 2017، 6:54م UTC](https://meta.discourse.org/t/docker-setup-for-development/72354/12 "2017-10-18T18:54:08Z")

</div>

If you take a look at the scripts in [discourse/bin/docker at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/bin/docker)

`boot_dev` creates and runs a container in detached mode, and `rails`/`rake`/etc utilizes `docker exec` to run the respective commands in the existing container, which are intended to make running those commands easier.

As for the `Dockerfile` question, it is answered in the README linked before: [discourse/bin/docker/README.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/bin/docker/README.md#where-is-the-container-imagedockerfile-defined)

* * *

There is a folder `d` at the project root symlinked to `bin/docker`, thus you can actually do `d/boot_dev`, `d/rails s`, etc.

---

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