I am running into a weird error when I set net=info for a Redis cluster composed of Redis containers. All containers are up and running on the same host box and netstat -tunap shows that all containers are listening on the correct ports. I am able to configure the cluster with redis-cli when I am on the box.
However, when I attempt to access via redis-cli from another box, I get a no route to host error. I see the same thing when I telnet, so this is not due to a redis-cli misconfiguration. So it seems the Docker container is only accepting local connections. Note: when I create my own custom Docker bridge network (via docker network create) I don’t get these no route to host errors.
Has anyone else encountered this issue with net=host? Any ideas/thoughts would be greatly appreciated.