You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do run mailman-* containers in the environment, orchestrated by SaltStack, so it is different from the reference docker-compose setup in some aspects.
In particular, all containers are sitting in two docker networks, bridge and mailman-net, which allows them to communicate locally and have resolvable local hostnames.
One of the side effects of such a setup is that hostname -i command returns:
# hostname -i
172.17.0.3 172.18.0.3
which then confuses configs where MM_HOSTNAME is used.
So, something like hostname -i | awk '{ print $NF }' could be a safer option(I'm picking the last IP in the list as that's what the internal network would get if ever used).
I actually ended up setting setting MM_HOSTNAME: '0.0.0.0', which seems to be a pretty universal option for the container(s) anyhow.
The text was updated successfully, but these errors were encountered:
Tag/version of Container Images
0.3., 0.4.
We do run
mailman-*
containers in the environment, orchestrated by SaltStack, so it is different from the referencedocker-compose
setup in some aspects.In particular, all containers are sitting in two docker networks,
bridge
andmailman-net
, which allows them to communicate locally and have resolvable local hostnames.One of the side effects of such a setup is that
hostname -i
command returns:which then confuses configs where
MM_HOSTNAME
is used.So, something like
hostname -i | awk '{ print $NF }'
could be a safer option(I'm picking the last IP in the list as that's what the internal network would get if ever used).I actually ended up setting setting
MM_HOSTNAME: '0.0.0.0'
, which seems to be a pretty universal option for the container(s) anyhow.The text was updated successfully, but these errors were encountered: