@@ -148,30 +148,30 @@ fails and Docker Engine returns an error.
148148
149149### Bridge driver options
150150
151- When creating a custom network, the default network driver (i.e. ` bridge ` ) has
152- additional options that can be passed. The following are those options and the
153- equivalent Docker daemon flags used for docker0 bridge:
154-
155- | Option | Equivalent | Description |
156- | --------------------------------------------------| -------------| -------------------------------------------------------|
157- | ` com.docker.network.bridge.name ` | - | Bridge name to be used when creating the Linux bridge |
158- | ` com.docker.network.bridge.enable_ip_masquerade ` | ` --ip-masq ` | Enable IP masquerading |
159- | ` com.docker.network.bridge.enable_icc ` | ` --icc ` | Enable or Disable Inter Container Connectivity |
160- | ` com.docker.network.bridge.host_binding_ipv4 ` | ` --ip ` | Default IP when binding container ports |
161- | ` com.docker.network.driver.mtu ` | ` --mtu ` | Set the containers network MTU |
162- | ` com.docker.network.container_iface_prefix ` | - | Set a custom prefix for container interfaces |
151+ When creating a custom ` bridge ` network, the following additional options can
152+ be passed. Some of these have equivalent flags that can be used on the dockerd
153+ command line or in ` daemon.json ` to configure the default bridge, ` docker0 ` :
154+
155+ | Network create option | Daemon option for ` docker0 ` | Description |
156+ | --------------------------------------------------| ----------------------------- | -------------------------------------------------------|
157+ | ` com.docker.network.bridge.name ` | - | Bridge name to be used when creating the Linux bridge |
158+ | ` com.docker.network.bridge.enable_ip_masquerade ` | ` --ip-masq ` | Enable IP masquerading |
159+ | ` com.docker.network.bridge.enable_icc ` | ` --icc ` | Enable or Disable Inter Container Connectivity |
160+ | ` com.docker.network.bridge.host_binding_ipv4 ` | ` --ip ` | Default IP when binding container ports |
161+ | ` com.docker.network.driver.mtu ` | ` --mtu ` | Set the containers network MTU |
162+ | ` com.docker.network.container_iface_prefix ` | - | Set a custom prefix for container interfaces |
163163
164164The following arguments can be passed to ` docker network create ` for any
165165network driver, again with their approximate equivalents to Docker daemon
166- flags used for the docker0 bridge:
167-
168- | Argument | Equivalent | Description |
169- | --------------| -----------------------------------| --------------------------------------------|
170- | ` --gateway ` | - | IPv4 or IPv6 Gateway for the master subnet |
171- | ` --ip-range ` | ` --fixed-cidr ` , ` --fixed-cidr-v6 ` | Allocate IPs from a range |
172- | ` --internal ` | - | Restrict external access to the network |
173- | ` --ipv6 ` | ` --ipv6 ` | Enable or disable IPv6 networking |
174- | ` --subnet ` | ` --bip ` , ` --bip6 ` | Subnet for network |
166+ flags used for the ` docker0 ` bridge:
167+
168+ | Network create option | Daemon option for ` docker0 ` | Description |
169+ | ----------------------- | -----------------------------------| --------------------------------------------|
170+ | ` --gateway ` | - | IPv4 or IPv6 Gateway for the master subnet |
171+ | ` --ip-range ` | ` --fixed-cidr ` , ` --fixed-cidr-v6 ` | Allocate IP addresses from a range |
172+ | ` --internal ` | - | Restrict external access to the network |
173+ | ` --ipv6 ` | ` --ipv6 ` | Enable or disable IPv6 networking |
174+ | ` --subnet ` | ` --bip ` , ` --bip6 ` | Subnet for network |
175175
176176For example, let's use ` -o ` or ` --opt ` options to specify an IP address binding
177177when publishing ports:
0 commit comments