[Question] bridge network and port mapping

[jhoogeboom]

[Question] bridge network and port mapping

[codekitchen]

The Dinghy proxy is an HTTP/HTTPS proxy, so it doesn't do anything to support non-HTTP protocols such as Redis. It listens on ports 80 and 443 on the Docker VM host, and reads the hostname to proxy to whatever backend port you expose, that's why your hello.docker is on port 80 not 8000.

Your redis.docker is being exposed on port 80 as well, but actually trying to connect to it won't work properly, since it's going through an HTTP proxy that doesn't understand the redis protocol.

[jhoogeboom]

Thanks for the clarification, I was hoping to get the linux style container-name addressing working on Macos, but I think I misunderstood Dinghy.

[jhoogeboom]

I guess the mentioned:

Sanity check!

$ docker run -it redis

is more about seeing if you can run docker commands on the connected VM rather than specifically about redis?

[codekitchen]

Well, Dinghy supports containers like redis in the same way that docker-machine does, but yeah I think that part of the README was written long before the Dinghy proxy existed.

Implementing container-name addressing would be cool, but I'm unlikely to ever do it myself, I'm not planning to add any big new features to Dinghy.