Okay I gave in and ran the --init command. I can confirm the container is running:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d2254e1374f5 discourse/discourse_dev:release "/sbin/boot" 24 minutes ago Up 24 minutes 0.0.0.0:1080->1080/tcp, 0.0.0.0:3000->3000/tcp, 0.0.0.0:9292->9292/tcp, 0.0.0.0:9405->9405/tcp discourse_dev
But I’m not seeing any record of it at any port. I’ve tried two browsers, localhost, 127.0.0.1, and 0.0.0.0 and there is no web application. The error is ERR_CONNECTION_RESET. I don’t see anything in iptables that would block this:
Chain DOCKER (3 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:9405
ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:9292
ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:3000
ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:socks
Update July 10, 2019
Thanks for everyone’s help - the issue was needing to issue that “unicorn” command, and I now have everything working. I also had to run rake admin:create in the start command, otherwise it wants an email confirmation (full repo here). The discourse_dev works too.