mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-09-20 17:14:09 +00:00
7593d969e3
Starting with Docker 20.10, `--hostname` seems to have the side-effect of making Docker's internal DNS server resolve said hostname to the IP address of the container. Because we were giving the mailer service a hostname of `matrix.DOMAIN`, all requests destined for `matrix.DOMAIN` originating from other services on the container network were resolving to `matrix-mailer`. This is obviously wrong. Initially reported here: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/748 We normally try to not use the public hostname (and IP address) on the container network and try to make services talk to one another locally, but it sometimes could happen. With this, we use a `matrix-mailer` hostname for the matrix-mailer container. My testing shows that it doesn't cause any trouble with email deliverability. |
||
|---|---|---|
| .. | ||
| matrix-base | ||
| matrix-bot-matrix-reminder-bot | ||
| matrix-bridge-appservice-discord | ||
| matrix-bridge-appservice-irc | ||
| matrix-bridge-appservice-slack | ||
| matrix-bridge-appservice-webhooks | ||
| matrix-bridge-mautrix-facebook | ||
| matrix-bridge-mautrix-hangouts | ||
| matrix-bridge-mautrix-telegram | ||
| matrix-bridge-mautrix-whatsapp | ||
| matrix-bridge-mx-puppet-discord | ||
| matrix-bridge-mx-puppet-instagram | ||
| matrix-bridge-mx-puppet-skype | ||
| matrix-bridge-mx-puppet-slack | ||
| matrix-bridge-mx-puppet-steam | ||
| matrix-bridge-mx-puppet-twitter | ||
| matrix-bridge-sms | ||
| matrix-client-element | ||
| matrix-common-after/tasks | ||
| matrix-corporal | ||
| matrix-coturn | ||
| matrix-dimension | ||
| matrix-dynamic-dns | ||
| matrix-email2matrix | ||
| matrix-jitsi | ||
| matrix-ma1sd | ||
| matrix-mailer | ||
| matrix-nginx-proxy | ||
| matrix-postgres | ||
| matrix-registration | ||
| matrix-synapse | ||
| matrix-synapse-admin | ||