Getting error "getaddrinfo ENOTFOUND mongo1" when trying to reach replication cluster on Docker through MongoDB Compass on Windows 10

[chris (Chris Dellaway)]

Really this comes down to the docker networking namespace and being able to resolve the hostnames. It also relates to the replicaset discovery when a client connects, the hostnames and ports returned by db.hello() is what the client will try and connect to.

@Pie_Leos

According to all the articles, I should be using this URI:

mongodb://127.0.0.1:27017,127.0.0.1:27018,127.0.0.1:27019/?replicaSet=my-replica-set

This would work if it wasn’t for docker. If you had multiple mongod on your local environment for example.

This is how I have have run a replset in docker and be able to connect from a local application.

MongoDB Replica Docker: Cannot connect on replica, only individual connection

The ports in your replicaset have to change too, to match the exposed ports. With a replicaset it is the config in the replica set that a client will connect to. I prefer to use different ip’s and keep 27017 as the port. My ports in compose look like:

ports extract docker-compose.yaml

services: mongo-0-a: ports: - 127.0.10.1:27017:27017 ... mongo-0-b: ports: - 127.0.10.2:27017:27017 ... mongo-0-c: ports: - 127.0.10.3:27017:27017 ...

Full Compose for reference

vers…