Redis [BUG] cluster internal MOVE commands makes host:port not reachable.

Describe the bug

I have setup cluster in a single container on ports 7000-7005. When trying to connect via redis_insight, 1- The redis_insight connects via service name of docker-compose, 2- The redis cluster issues move command to another node (host and port, eg 127.0.0.1:7003) which is not accessible to services outside of this container.

To reproduce

Setup cluster in a single container on ports 7000-7005. Try connecting via redis_insight or any other service, It won't connect.

Expected behavior

It should be able to connect via exposed ports and internal MOVE command should bind to host, not 127.0.0.1

Additional information

I am following this approach: https://www.youtube.com/watch?v=N8BkmdZzxDg

Comment From: zuiderkwast

When you say "MOVE command", do you mean "MOVED redirect"?

I'm guessing the ports 7000-7005 are not exposed outside of the container, so therefore the client can't access them. You can make docker expose these ports on the host's network by running docker with --net=host.