# Docker setup for development

**URL:** <https://meta.discourse.org/t/docker-setup-for-development/72354>\
**Category:** Development\
**Created:** [2017 年 10 月 18 日午後 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:** 14

<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:** [2017 年 10 月 18 日午後 7:28 UTC](https://meta.discourse.org/t/docker-setup-for-development/72354/14 "2017-10-18T19:28:06Z")

</div>

Have you ran `d/boot_dev --init` first? If so, then `d/rails`, `d/rake`, etc should work fine.

> [@drew0101](#):
>
> Is there any reason to use docker exec over d/ ?

Of course you can manage/interact with the container directly yourself, but I’d say the helper scripts are … helpful? I hack on Discourse locally with the Docker setup, and the helper scripts are all I need so far.

* * *

EDIT: just realized your question was regarding using `docker exec` specifically, in that case, I recommand checking out [the official reference](https://docs.docker.com/engine/reference/commandline/exec/) (or the helper scripts themselves) and then you will see the necessary syntax to interact with an existing container.

---

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