meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:docker:network [2020/03/17 07:51] – niziaklinux:docker:network [2020/03/20 20:13] (current) – niziak
Line 10: Line 10:
  
 By default docker try to choose not conflicting addressing scheme: By default docker try to choose not conflicting addressing scheme:
-<code> +<code>172.17.0.0/16", 172.18.0.0/16", "172.19.0.0/16", "172.20.0.0/14", "172.24.0.0/14" "172.28.0.0/14", "192.168.0.0/16"</code>
-172.17.0.0/16", 172.18.0.0/16", "172.19.0.0/16", +
-"172.20.0.0/14", "172.24.0.0/14" "172.28.0.0/14", "192.168.0.0/16" +
-</code>+
  
 but sometimes it doesn't work. but sometimes it doesn't work.
Line 27: Line 24:
 Will assign 16 bit class for docker daemon, and docker daemon will create 24 bit network per each network. Will assign 16 bit class for docker daemon, and docker daemon will create 24 bit network per each network.
  
 +
 +Another example:
 +<file json | /etc/docker/daemon.json>
 +{
 +  "bip": "10.200.0.1/24",
 +  "default-address-pools":[
 +    {"base":"10.201.0.0/16","size":24},
 +    {"base":"10.202.0.0/16","size":24}
 +  ]
 +}
 +</file>
 ====== How to connect container to real network ====== ====== How to connect container to real network ======
  
Line 97: Line 105:
       * Shared MAC address can affect DHCP operations. If your VMs or containers use DHCP to acquire network settings, make sure they use unique ClientID in the DHCP request and ensure your DHCP server assigns IP addresses based on ClientID, not client’s MAC address.       * Shared MAC address can affect DHCP operations. If your VMs or containers use DHCP to acquire network settings, make sure they use unique ClientID in the DHCP request and ensure your DHCP server assigns IP addresses based on ClientID, not client’s MAC address.
       * Autoconfigured EUI-64 IPv6 addresses are based on MAC address. All VMs or containers sharing the same parent interface will auto-generate the same IPv6 address. Ensure that your VMs or containers use static IPv6 addresses or IPv6 privacy addresses and disable SLAAC.       * Autoconfigured EUI-64 IPv6 addresses are based on MAC address. All VMs or containers sharing the same parent interface will auto-generate the same IPv6 address. Ensure that your VMs or containers use static IPv6 addresses or IPv6 privacy addresses and disable SLAAC.
 +
 +**NOTE**: Both modes requires support from HW to use multiple MAC. Without it device needs to be switched into promiscuous mode, which is not easy. Working methods:
 +    * Virtualbox on host machine - during host machine startup it sets own driver 
  
 ==== macvlan details ==== ==== macvlan details ====