I’m working on trying to set up a test Discourse instance in a VM so I can work on importing from another software. I’m new to Docker, Discourse, and Ruby, so I’m not yet familiar with what’s going on in the background. So far, I’ve forked the discourse_docker repo and then used that following the instructions here (using my own local Ubuntu VM instead of a cloud instance): discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub
After setup, according to netstat, it appears my local VM here has set up the container in such a way that ports 80 and 443 are only listening on the IPv6 IP. I don’t use IPv6 locally, so I can’t access the Discourse instance. How can I correct this? I looked in app.yml but there don’t appear to be any bind settings in there. I’ve search for anyone having a similar issue - there was one hit from I think 2015 where the resolution was to go change the DNS configuration inside the container itself. This sounds like a Bad Idea™ so I’m hoping for something a bit less hacky.