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
docker_daemon_options:
experimental: trueipv6: trueip6tables: truefixed-cidr-v6: "REDACTED::/64"# get something from https://simpledns.plus/private-ipv6
With this I was able to remove the baibot extra hosts
Any component in a docker container relies on the docker networking because all components are connected via bridged networks
Any component that makes discovery of the matrix server itself will use the DNS records returned by docker
If docker (and/or its bridged networks) have IPv4-only, then you won't get IPv6 working inside the containers.
Both Baibot and Postmoogle are capable of working with IPv4 and IPv6, the question is proper network configuration. Unfortunately, IPv6 doesn't always work well with docker.
Describe the bug
A clear and concise description of what the bug is.
My homeserver is IPv6 only, the machine is dualstack but only ipv6 is public and part of my DNS entry.
Both baibot and postmoogle fail to boot because they resolve my matrix.example.com to IPv6 no have no way to reach it.
I had to add the following lines to my vars to trick the services into resolve the homeserver address using the local address
To Reproduce
matrix_server_fqn_matrix
must only have an IPv6 entry, no ipv4My
vars.yml
file looks like this:Expected behavior
baibot and postmoogle starts.
I forgot to take the exact error of postmoogle, but for baibot the error in the logs is this one
Matrix Server:
Ansible:
If your problem appears to be with Ansible, tell us:
ansible --version
)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: