Signed-off-by: Malte Janduda <mail@janduda.net>
| ... | ... |
@@ -578,9 +578,10 @@ for Docker. When adding a third host you would add a route for the subnet |
| 578 | 578 |
|
| 579 | 579 |
Remember the subnet for Docker containers should at least have a size of `/80`. |
| 580 | 580 |
This way an IPv6 address can end with the container's MAC address and you |
| 581 |
-prevent ARP cache invalidation issues in the Docker layer. So if you have a |
|
| 582 |
-`/64` for your whole environment use `/68` subnets for the hosts and `/80` for |
|
| 583 |
-the containers. This way you can use 4096 hosts with 16 `/80` subnets each. |
|
| 581 |
+prevent NDP neighbor cache invalidation issues in the Docker layer. So if you |
|
| 582 |
+have a `/64` for your whole environment use `/68` subnets for the hosts and |
|
| 583 |
+`/80` for the containers. This way you can use 4096 hosts with 16 `/80` subnets |
|
| 584 |
+each. |
|
| 584 | 585 |
|
| 585 | 586 |
Every configuration in the diagram that is visualized below the dashed line is |
| 586 | 587 |
handled by Docker: The `docker0` bridge IP address configuration, the route to |