This appears to be specific to non-standard installs that simultaneously:
-
Didn’t use
./discourse-setupand created a yml file manually -
Are using a reverse proxy
-
This reverse proxy is magically configured using a docker container name
I’d advise against changing the current deterministic container name for everyone to address this corner case, unless it can also happens by simply adding an extra dot to the yml file name.