Docker Networking Explained September 3, 2018 by scmmishra https://codability.in/docker-networking-explained/
5 thoughts on “Docker Networking Explained”
I’m a bot, *bleep*, *bloop*. Someone has linked to this thread from another place on reddit:
– [/r/kubernetes] [Docker Networking Explained](https://www.reddit.com/r/kubernetes/comments/9cpwuq/docker_networking_explained/)
*^(If you follow any of the above links, please respect the rules of reddit and don’t vote in the other threads.) ^\([Info](/r/TotesMessenger) ^/ ^[Contact](/message/compose?to=/r/TotesMessenger))*
Thanks for this, I’m only just getting started, and am planning to run a few containers side by side, hopefully with several of them running traffic through a container running a VPN, and while I had read documentation around this, I was having trouble understanding just by reading it (I have trouble understanding some concepts unless I’ve drawn out a diagram or list or something to demonstrate what I’m trying to understand) so having a few diagrams helps.
Useful info, thanks for posting, but needs some serious proofreading.
I have a question around docker-networking scenario and adding it here due to context. I am setting up 2 instances (AWS ec2) with each running 3 containers of Prometheus/grafana/AlertManager. One of the 3 services needs peering with the other service on different host and I am using docker-compose (not swarm) to set these services up. From what I understood this is not possible with default docker-bridge network that compose brings up to tie this services? I tried exposing the ports but it still tries to refer to the docker ip subnet?
Good info provided in this article, however linking containers is deprecated. [User-defined networks](https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks) should be used instead.