I’ve tried to setup my Discourse development environment the Docker way, but I’ve realized that boot_env script tries to pull a non existent discourse/discourse_dev:latest docker image. Instead, a discourse/dev:latest image exists in Docker Hub, but it is outdated (version 1.0.13). So I’ve tried to build it myself running $ sudo ruby build.rb -i discourse_dev But when I run $ ./bin/docker/boot_env --init I get an error message regarding PostgreSQL: Migrating database... URGENT: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Failed to initialize site default URGENT: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Failed to initialize site default rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Any ideas to fix it?

[תמונה] zuzust: So I’ve tried to build it myself running $ sudo ruby build.rb -i discourse_dev So the image build successfully for you, good to know. Let me take a look at this.

[תמונה] zuzust: I’ve tried to setup my Discourse development environment the Docker way, but I’ve realized that boot_env script tries to pull a non existent discourse/discourse_dev:latest docker image. Instead, a discourse/dev:latest image exists in Docker Hub, but it is outdated (version 1.0.13). I too am interested in an official well maintained docker image for development where I can simply mount my working directory and map a port then land into the bash prompt of the container. It should ship with some setup scripts to make the engines cracking inside. Additionally, it would be good to have a developer documentation maintained similar to the one at: https://github.com/discourse/discourse/blob/master/docs/DEVELOPER-ADVANCED.md

I tried the following the Developing using Docker guide: $ cd /tmp $ git clone https://github.com/discourse/discourse.git $ cd discourse $ ./bin/docker/boot_dev --init Realized that it is looking for discourse/discourse_dev:latest image which doesn’t exist in the DockerHub repository. So I decided to build it locally and tag accordingly: $ cd /tmp $ git clone https://github.com/discourse/discourse_docker.git $ cd discourse_docker $ docker build -t discourse/discourse_dev image/discourse_dev It complained about missing template files and failed to build. So I looked at the corresponding Dockerfile to find out what files are being added then I copied them from the template directory: $ cp templates/redis.template.yml templates/postgres.template.yml image/discourse_dev $ docker build -t discourse/discourse_dev image/discourse_dev Voila! Success! :slight_smile: Going back to the main discourse directory to setup the work environment: $ cd /tmp/discourse $ ./bin/docker/boot_dev --init Container spun and gems bundled, but database migration failed: Bundle complete! 98 Gemfile dependencies, 184 gems now installed. Use `bundle show [gemname]` to see where a bundled gem is installed. Post-install message from certified: IMPORTANT: Remember to use the included executable `certifed-update` regularly to keep your certificate bundle up to date. Migrating database... Rails Error: Unable to access log file. Please ensure that /src/log/development.log exists and is writable (ie, make it writable for user and group: chmod 0664 /src/log/development.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed. rake aborted! Errno::EACCES: Permission denied @ rb_sysopen - /src/tmp/ember-rails/ember.js /src/config/environment.rb:5:in ` ' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) Creating admin user... Rails Error: Unable to access log file. Please ensure that /src/log/development.log exists and is writable (ie, make it writable for user and group: chmod 0664 /src/log/development.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed. rake aborted! Errno::EACCES: Permission denied @ rb_sysopen - /src/tmp/ember-rails/ember.js /src/config/environment.rb:5:in ` ' Tasks: TOP => admin:create => environment (See full trace by running task with --trace) So, I decided to dive inside the running container and run the migrations manually: $ docker exec -it discourse_dev bash # cd src # rake db:migrate But the migrations did not succeed. URGENT: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Failed to initialize site default URGENT: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Failed to initialize site default rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? Tasks: TOP => db:migrate (See full trace by running task with --trace) From here I am not sure what else should I try.

For last few days I was looking into the Discourse’s code base and trying to understand it’s working so that I can make my hands dirty with some development and contribution. However, not being able to setup the development environment, I can’t do much. I hope @Falco will be able to resolve it sooner than later. The commands that I listed in a sequence in my last post should be reproducible.

[תמונה] ibnesayeed: I hope @Falco will be able to resolve it sooner than later. Sorry about that, we found a nasty bug with our memory allocation with lastest docker image and I’ll fix that before getting the dev image out. I started looking at it tough, and it’s mostly done, we just need to get PostgreSQL to work.

[תמונה] ibnesayeed: For last few days I was looking into the Discourse’s code base and trying to understand it’s working so that I can make my hands dirty with some development and contribution. However, not being able to setup the development environment, I can’t do much. While it’s great that you’re testing the new Docker based workflow, keep in mind that this isn’t our default development environment yet. Our beginners guide for Ubuntu and Mac still work fine. [תמונה] Contributing to Discourse development Contributing bookmark This guide is designed for those who wish to contribute to the Discourse open-source project, detailing the setup and conventions necessary for effective collaboration. person_raising_hand Required user level: While anyone can contribute code, you will need to be familiar with Ruby and JavaScript. Summary This documentation will cover the following: Setting up your development environment Understanding where to begin contributing Creating and working with Discourse plugins Co…

Meanwhile, I have setup a fullly functional and standard Docker development environment, dockerizing the set of instructions in Discourse Advanced Developer Install Guide. Check it out here: https://github.com/adab1ts/discourse/commit/f2ff9aecf31794d032349646a3dfc8bd94387363 Changes in development workflow: Development First time: $ docker-compose build $ docker-compose run discourse bundle exec rake db:create db:migrate $ docker-compose run discourse bundle exec rake admin:create $ docker-compose up -d $ docker-compose exec discourse mailcatcher --ip=0.0.0.0 $ docker-compose exec discourse bundle exec sidekiq -q critical,low,default -d -l log/sidekiq.log $ docker-compose stop Common workflow: $ docker-compose start $ docker-compose exec discourse mailcatcher --ip=0.0.0.0 $ docker-compose exec discourse bundle exec sidekiq -q critical,low,default -d -l log/sidekiq.log $ docker-compose stop Test $ docker-compose run -e "RAILS_ENV=test" discourse bundle exec rake db:create db:migrate $ docker-compose run discourse bundle exec rake autospec p l=5 To link services successfully you have to reference their names as host values in config/database.yml and config/discourse.{development,test}.conf: # config/discourse.development.conf # comma delimited list of emails that have developer level access developer_emails = carles@adabits.org # redis server address redis_host = redis # redis server port redis_port = 6379 # redis slave server address redis_slave_host = # redis slave server port redis_slave_port = 6379 # redis database redis_db = 0 # redis password redis_password = # redis sentinels eg # redis_sentinels = 10.0.0.1:26381,10.0.0.2:26381 redis_sentinels =

FROM buildpack-deps:xenial not using our base image loses out tons of the advantages of using docker in dev. We are super careful to include all the fiddly dependencies in our docker image including image magick, nginx and plenty of other bits and pieces. compose is fine if that is your thing but you should base of our base image or discourse/discourse image.

[תמונה] ibnesayeed: I too am interested in an official well maintained docker image for development where I can simply mount my working directory and map a port then land into the bash prompt of the container. This sort of works, but there are some issues that need careful consideration. Especially the fact the UIDs inside docker do not necessarily the UIDs outside of docker, it is a delicate game that you need to play.

Issue regarding Docker development image

Development

sam (Sam Saffron) 5 בדצמבר,‏ 2016,‏ 5:24am 5

@Falco can you play around with the dev image and see if you can get it going, maybe document it a bit better?

נושא		תגובות	צפיות
Install Discourse for development using Docker Developer Guides docker , dev-install , how-to	226	95089	22 במאי,‏ 2026
Running Discourse on Docker for Mac Development	46	14913	14 במאי,‏ 2020
Using a launcher built docker image in docker-compose Development	30	8535	27 בספטמבר,‏ 2024
Docker setup for development Development	16	6593	19 באוקטובר,‏ 2017
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	211	41855	13 ביולי,‏ 2025

Issue regarding Docker development image

נושאים קשורים