mirror of https://github.com/docker/docs.git
docs: enhance html output (#16076)
* docs: remove some leading space * style: fix whitespace inconsistency - double spaces in docker commands - inconsistent indentation in multiline commands and paragraphs - trailing spaces
This commit is contained in:
parent
2dbc818eaa
commit
28b19178aa
|
@ -330,7 +330,7 @@ $$ ip a show eth0
|
|||
gateway points to the containers `eth0` device. See below for CLI output
|
||||
of `ip route` or `ip -6 route` from inside an L3 container for details.
|
||||
|
||||
The mode ` -o ipvlan_mode=l3` must be explicitly specified since the default
|
||||
The mode `-o ipvlan_mode=l3` must be explicitly specified since the default
|
||||
IPvlan mode is `l2`.
|
||||
|
||||
The following example does not specify a parent interface. The network drivers
|
||||
|
@ -377,13 +377,13 @@ host eth interface.
|
|||
## Dual stack IPv4 IPv6 IPvlan L2 mode
|
||||
|
||||
- Not only does Libnetwork give you complete control over IPv4 addressing, but
|
||||
it also gives you total control over IPv6 addressing as well as feature parity
|
||||
between the two address families.
|
||||
it also gives you total control over IPv6 addressing as well as feature parity
|
||||
between the two address families.
|
||||
|
||||
- The next example will start with IPv6 only. Start two containers on the same
|
||||
VLAN `139` and ping one another. Since the IPv4 subnet is not specified, the
|
||||
default IPAM will provision a default IPv4 subnet. That subnet is isolated
|
||||
unless the upstream network is explicitly routing it on VLAN `139`.
|
||||
VLAN `139` and ping one another. Since the IPv4 subnet is not specified, the
|
||||
default IPAM will provision a default IPv4 subnet. That subnet is isolated
|
||||
unless the upstream network is explicitly routing it on VLAN `139`.
|
||||
|
||||
```console
|
||||
# Create a v6 network
|
||||
|
|
Loading…
Reference in New Issue