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

<div class="post-metadata">

### Author: ![bitmage](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bitmage/32/389881_2.png) [@bitmage](https://meta.discourse.org/u/bitmage)
#### Post date: [March 20, 2025, 2:39pm UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/311 "2025-03-20T14:39:27Z")

</div>

I did not have very good luck with symlinking my plugins folder:

> [@Can we use \`.gjs\` for route templates?](https://meta.discourse.org/t/can-we-use-gjs-for-route-templates/357046/11):
>
> I found in the d/rails s logs: No such file or directory @ rb\_sysopen - /src/app/assets/stylesheets/plugin-cf.scss. So even though the plugin is symlinked into the /plugins folder as county-fence, and my plugin is explicitly named county-fence in plugins.rb, some code is reading the underlying directory name plugin-cf and making assumptions about what the compiled CSS name for my plugin is. Is this a bug or a feature? smiley I think the moral of this story is do not under any circumstances…

I ended up moving to a normal folder as a result (see my last comment in that thread).

I think there are some incompatibilities currently with Docker volumes, file watchers, and symlinks.

---

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