Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update work-with-networks.md #5259

Merged
merged 1 commit into from
Nov 9, 2017
Merged

Update work-with-networks.md #5259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions engine/userguide/networking/work-with-networks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down