From f6ecba104556f4c68b8ad11ee8c2e6b2a27b87ff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim=20D=C3=BCsterhus?= Date: Thu, 12 May 2016 23:18:58 +0200 Subject: [PATCH] Clarify that --ip does not work with IPv6 in docker run MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Closes docker/docker#22707 Signed-off-by: Tim Düsterhus --- docs/userguide/networking/work-with-networks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/userguide/networking/work-with-networks.md b/docs/userguide/networking/work-with-networks.md index 148885d263..5071b6933e 100644 --- a/docs/userguide/networking/work-with-networks.md +++ b/docs/userguide/networking/work-with-networks.md @@ -228,7 +228,8 @@ $ docker run --net=isolated_nw --ip=172.25.3.3 -itd --name=container3 busybox As you can see you were able to specify the ip address for your container. As long as the network to which the container is connecting was created with a user specified subnet, you will be able to select the IPv4 and/or IPv6 address(es) -for your container when executing `docker run` and `docker network connect` commands. +for your container when executing `docker run` and `docker network connect` commands +by respectively passing the `--ip` and `--ip6` flags for IPv4 and IPv6. The selected IP address is part of the container networking configuration and will be preserved across container reload. The feature is only available on user defined networks, because they guarantee their subnets configuration does not change across daemon reload.