Que: How does Docker Host network configuration look like after Docker container is created? Que: How does Docker Host network configuration look like after Docker is installed? Que: How does traditional Docker Host network look like before Docker is installed? By binding every veth* interface to the docker0 bridge, Docker creates a virtual subnet shared between the host machine and every Docker container. It gives one of the peers to the container to become its eth0 interface and keeps the other peer, with a unique name like vethAQI2QT, out in the namespace of the host machine.
Que: How does ifconfig look like?Įvery time Docker creates a container, it creates a pair of “peer” interfaces that are like opposite ends of a pipe - a packet sent on one will be received on the other. The MAC address is generated using the IP address allocated to the container to avoid ARP collisions, using a range from 02:42:ac:11:00:00 to 02:42:ac:11:ff:ff. By default it chooses a 16-bit netmask providing 65,534 addresses for the host machine and its containers. It randomly chooses an address and subnet from the private range defined by RFC 1918 that are not in use on the host machine, and assigns it to docker0. Que: Where does the 172.17.42.x come from? Que: How does Docker Networking look like? Hope it is helpful for all Docker beginners.
I have put it through Q&A which are usually been asked or raised during the various meetups, seminars, webinars and presentations. I have tried to put it in very simple language so that laymen can understand how Docker networking is different from traditional bare metal OR virtual networking.
Docker for mac 0.0.0.0 ip address series#
This is a tutorial series for understanding how Docker Networking really works.
0 kommentar(er)
