@codinghorror That’s all well and great, but then, if standard standalone installs is the only way Discourse is supposed to operate, why provide support for yml container configuration in ./containers, and including examples of this in ./samples? The file I used is fully commented with instructions on operation, specifically this area:
# any extra arguments for Docker?
# docker_args:
The only thing I am using is:
docker_args: "--network reverse-proxy"
Which again, has been working great for a year now. So, obviously something has changed. Please understand I am not trying to be confrontational (it would be kind of silly since I am asking for help), but I am indeed trying to make the point that I am using options that are made available through the Discourse samples.
Perhaps if I understood how that mac address is being generated it could point me to an environment change issue, that’s what I’m hoping.
I see this in launcher:
if [ -z "$SKIP_MAC_ADDRESS" ] ; then
mac_address="--mac-address $($docker_path run $user_args -i --rm -a stdout -a stderr $image /bin/sh -c "echo $hostname | md5sum | sed 's/^\(..\)\(..\)\(..\)\(..\)\(..\).*$/02:\1:\2:\3:\4:\5/'")"
fi
Will dissect and see if I can figure it out.
UPDATE: And looking at this, I see that I can use --skip-mac-address. Doing this brings up my instance just fine, so it seems the process that figures out the mac address is the issue.