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
manual override of the start-up arguments to use --bind_ip::,0.0.0.0
In both cases Mongo listens on just 0.0.0.0:27017. Connections from other containers in a docker-compose built environment may result in connection issues (if the app only tries IPv6 and does not fall back to IPv4).
I had to add the command: mongod --auth --ipv6 --bind_ip ::,0.0.0.0 line to my docker-compose.yaml to get this working.
Proposal:
the --ipv6 argument should be always added as part of the docker-entrypoint.sh when the bind-all argument is added by the docker-entrypoint.sh and the container is IPv6-enabled
the --ipv6 argument should be always added as part of the docker-entrypoint.sh when the bind_ip argument contains an IPv6 address.
Hi everyone,
I have encountered a bug where the official Mongo image does not properly enable MongoDB to listen on IPv6 address(es).
I have tried two cases:
docker-entrypoint.sh
sets "--bind-all")--bind_ip::,0.0.0.0
In both cases Mongo listens on just
0.0.0.0:27017
. Connections from other containers in a docker-compose built environment may result in connection issues (if the app only tries IPv6 and does not fall back to IPv4).I had to add the
command: mongod --auth --ipv6 --bind_ip ::,0.0.0.0
line to mydocker-compose.yaml
to get this working.Proposal:
--ipv6
argument should be always added as part of thedocker-entrypoint.sh
when thebind-all
argument is added by thedocker-entrypoint.sh
and the container is IPv6-enabled--ipv6
argument should be always added as part of thedocker-entrypoint.sh
when thebind_ip
argument contains an IPv6 address.Thank you for looking into this issue.
Environment:
The text was updated successfully, but these errors were encountered: