User network does not work with IPv6
(cherry picked from commit ab090291dd15c76687672fec10eb9f4106c1cb21)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
| ... | ... |
@@ -228,7 +228,8 @@ $ docker run --net=isolated_nw --ip=172.25.3.3 -itd --name=container3 busybox |
| 228 | 228 |
As you can see you were able to specify the ip address for your container. |
| 229 | 229 |
As long as the network to which the container is connecting was created with |
| 230 | 230 |
a user specified subnet, you will be able to select the IPv4 and/or IPv6 address(es) |
| 231 |
-for your container when executing `docker run` and `docker network connect` commands. |
|
| 231 |
+for your container when executing `docker run` and `docker network connect` commands |
|
| 232 |
+by respectively passing the `--ip` and `--ip6` flags for IPv4 and IPv6. |
|
| 232 | 233 |
The selected IP address is part of the container networking configuration and will be |
| 233 | 234 |
preserved across container reload. The feature is only available on user defined networks, |
| 234 | 235 |
because they guarantee their subnets configuration does not change across daemon reload. |