From 19dd8d1b1b7faebab89ca0b6eef922c5a4c6031b Mon Sep 17 00:00:00 2001 From: Jim Armstrong Date: Thu, 9 Nov 2017 11:43:24 -0600 Subject: [PATCH] Update work-with-networks.md Corresponds to issue #34873: clarifies that the IP address used for binding should be an actual IP on the user's host, and not literally 172.23.0.1 --- engine/userguide/networking/work-with-networks.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/engine/userguide/networking/work-with-networks.md b/engine/userguide/networking/work-with-networks.md index 41d0c525697..a93af11e4bc 100644 --- a/engine/userguide/networking/work-with-networks.md +++ b/engine/userguide/networking/work-with-networks.md @@ -123,9 +123,10 @@ The following arguments can be passed to `docker network create` for any network | `--internal` | - | Restrict external access to the network | | `--ipv6` | `--ipv6` | Enable IPv6 networking | -The following example uses `-o` to bind to a specific IP address when binding +The following example uses `-o` to bind to a specific IP address available on the host when binding ports, then uses `docker network inspect` to inspect the network, and finally -attaches a new container to the new network. +attaches a new container to the new network. Note that you should replace the IP address `172.23.0.1` shown in the +example with an IP address available on a network interface in your host. ```bash $ docker network create -o "com.docker.network.bridge.host_binding_ipv4"="172.23.0.1" my-network