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?

[图片] 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.

[图片] sam: 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. I wrote that before I realized that there is a docker image for development that has some workflow in place already.

It is just a temporary solution to face the issues reported in my first comment. I will adopt the official docker workflow as soon as it is fixed. In case you weren’t aware of, notice that bin folder is not being tracked by git (discourse/.gitignore at main · discourse/discourse · GitHub) so any changes to bin/docker/boot_dev are being ignored. discourse/discourse image is not for development as it excludes the gems in development group of Gemfile (discourse_docker/image/discourse/Dockerfile at master · adab1ts/discourse_docker · GitHub). discourse/base is a bit time consuming to reason about, that’s why I followed the steps in your easy to follow Discourse Advanced Developer Install Guide. But again, I’m not interested in my own way. As I said before, I will adopt the official docker workflow as soon as it is fixed.

I spent some time cleaning stuff up today and have this all working. Follow the instructions here and you should be good: bin/docker/README.md main # Developing using Docker Since Discourse runs in Docker, why not develop there? If you have Docker installed, you should be able to run Discourse directly from your source directory using a Discourse development container. You can find installation instructions and related discussion in this meta topic: https://meta.discourse.org/t/beginners-guide-to-install-discourse-for-development-using-docker/102009 ##### Where is the container image/Dockerfile defined? The Dockerfile comes from [discourse/discourse_docker on GitHub](https://github.com/discourse/discourse_docker), in particular [image/discourse_dev](https://github.com/discourse/discourse_docker/tree/master/image/discourse_dev). (if you tried this in the past try running sudo rm -fr tmp/postgres and docker pull discourse/discourse_dev to clean up stuff) Let me know how you go.

[图片] sam: Let me know how you go. It looks like the said image is still not in the DockerHub. Ideally it should be configured as an auto-build there. $ ./bin/docker/rails s Error response from daemon: No such container: discourse_dev

Have you tried readme, step by step?

Issue regarding Docker development image

Development

ibnesayeed (Sawood Alam) 2016 年12 月 13 日 00:19 23

@sam, the following two PRs should do the trick.

https://github.com/discourse/discourse_docker/pull/317

https://github.com/discourse/discourse/pull/4598

话题		回复	浏览量
Install Discourse for development using Docker Developer Guides docker , dev-install , how-to	226	94854	2026 年5 月 22 日
Running Discourse on Docker for Mac Development	46	14882	2020 年5 月 14 日
Using a launcher built docker image in docker-compose Development	30	8516	2024 年9 月 27 日
Docker setup for development Development	16	6567	2017 年10 月 19 日
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	211	41735	2025 年7 月 13 日

Issue regarding Docker development image

相关话题