Install Discourse for Development using Docker is Failed

AI-generated summary

A user named 영광_임 is struggling to install Discourse for development using Docker, following the official guide. After cloning the repo and running ./bin/docker/boot_dev --init and ./bin/docker/unicorn, they expect to see Discourse at http://localhost:9777 (changed from 9292 due to port conflict), but nothing appears. The logs suggest the server is running, with workers ready and listening on port 9777. justin suspects the issue may be that port 9777 is blocked or closed on the development machine. 영광_임 asks if they should stop the Docker container, and later admits confusion, asking for clarification. icanhasr00t advises checking if port 9777 is actually open using netstat -n l | grep 9777. 영광_임 confirms the port was changed from 9292 to 9777 to avoid collision, but the issue persists. The core problem remains unresolved — the server appears to be running, but the site is not accessible, likely due to a network or port binding issue.

I fail…
Install Discourse for Development using Docker

  • clone Discourse
git clone https://github.com/discourse/discourse.git ~/discourse
  • start dev
cd discourse
./bin/docker/boot_dev --init
./bin/docker/unicorn

open a browser on http://localhost:9777 and I don’t should see Discourse.
why??

(It was changed to 9777 due to port collision.)

Detail :

y@y-VirtualBox:~/discourse$ sudo ./bin/docker/unicorn -x
Running without sidekiq
I, [2019-07-22T17:51:53.863457 #795]  INFO -- : Refreshing Gem list
WARNING: It looks like your discourse plugins have recently changed.
It is highly recommended to remove your `tmp` directory, otherwise
plugins might not work.

Starting CSS change watcher
I, [2019-07-22T17:51:57.024178 #795]  INFO -- : listening on addr=0.0.0.0:9777 fd=13
I, [2019-07-22T17:52:02.327320 #795]  INFO -- : master process ready
I, [2019-07-22T17:52:05.364922 #884]  INFO -- : worker=0 ready
I, [2019-07-22T17:52:05.397963 #894]  INFO -- : worker=1 ready
I, [2019-07-22T17:52:06.423513 #904]  INFO -- : worker=2 ready
.............

Is it running?

Looks like it to me. Have you checked for port 9777 being closed on the dev machine?

docker stop discourse_dev??

I don’t know
Please explain

Please check if port 9777 is properly open.

netstat -nl | grep 9777

Run this command to see if anything is matched.

Originally, the crash occurred at 9292, and it was changed to 9777