# Install Discourse for development using Docker **URL:** \ **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:** 302
**Author:** ![pento](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pento/32/450661_2.png) [@pento](https://meta.discourse.org/u/pento)\ **Post date:** [October 19, 2024, 4:14am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/302 "2024-10-19T04:14:42Z")
Done! > > > \## ✨ What's Happening? > > When attempting to \[set up the Docker development envi…ronment\](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009), I was seeing the following error when running \`d/boot\_dev --init\`: > > \`\`\` > ActiveRecord::NoDatabaseError: We could not find your database: discourse\_development. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError) > \`\`\` > > Running \`db:create\` before the \`db:migrate\` fixed this issue for me. It appears to be safe to run \`db:create\` even if the database already exists, running \`d/rake db:create\` locally shows an info message at the database already exists, but doesn't exit with an error. > > \## 👑 Testing > > If you already have a Docker dev environment setup, you will need to run \`docker stop discourse\_dev && docker rm discourse\_dev\` first to remove it. > > Before switching to this PR, run through the \[Docker setup instructions\](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009) to confirm that you run into this error. > > After switching to this PR, run \`docker stop discourse\_dev && docker rm discourse\_dev\`, then follow the Docker setup instructions again. --- _[View the full topic](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009)._