mirror of
https://github.com/clearlinux/docker.git
synced 2026-10-03 15:28:35 +00:00
enhancing set-macaddress docu
Signed-off-by: Malte Janduda <mail@janduda.net>
This commit is contained in:
committed by
Malte Janduda
parent
f2df38050e
commit
971fc2253a
@@ -105,7 +105,7 @@ Finally, several networking options can only be provided when calling
|
||||
[How Docker networks a container](#container-networking)
|
||||
|
||||
* `--mac-address=MACADDRESS...` — see
|
||||
[How docker networks a container](#container-networking)
|
||||
[How Docker networks a container](#container-networking)
|
||||
|
||||
* `-p SPEC` or `--publish=SPEC` — see
|
||||
[Binding container ports](#binding-ports)
|
||||
@@ -540,13 +540,13 @@ The steps with which Docker configures a container are:
|
||||
separate and unique network interface namespace, there are no
|
||||
physical interfaces with which this name could collide.
|
||||
|
||||
4. Set the interface's mac address according to the `--mac-address`
|
||||
4. Set the interface's MAC address according to the `--mac-address`
|
||||
parameter or generate a random one.
|
||||
|
||||
5. Give the container's `eth0` a new IP address from within the
|
||||
bridge's range of network addresses, and set its default route to
|
||||
the IP address that the Docker host owns on the bridge. If available
|
||||
the IP address is generated from the MAC address. This prevents arp
|
||||
the IP address is generated from the MAC address. This prevents ARP
|
||||
cache invalidation problems, when a new container comes up with an
|
||||
IP used in the past by another container with another MAC.
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ total memory available (`MemTotal`).
|
||||
|
||||
`POST /containers/create`
|
||||
**New!**
|
||||
You can define the container's MAC address by providing a MacAddress key-value pair.
|
||||
You can set the new container's MAC address explicitly.
|
||||
|
||||
## v1.15
|
||||
|
||||
|
||||
@@ -140,7 +140,7 @@ example, `docker run ubuntu:14.04`.
|
||||
'container:<name|id>': reuses another container network stack
|
||||
'host': use the host network stack inside the container
|
||||
--add-host="" : Add a line to /etc/hosts (host:IP)
|
||||
--mac-address="" : Sets the container's ethernet device's mac address
|
||||
--mac-address="" : Sets the container's ethernet device's MAC address
|
||||
|
||||
By default, all containers have networking enabled and they can make any
|
||||
outgoing connections. The operator can completely disable networking
|
||||
@@ -151,9 +151,9 @@ networking. In cases like this, you would perform I/O through files or
|
||||
Your container will use the same DNS servers as the host by default, but
|
||||
you can override this with `--dns`.
|
||||
|
||||
By default a random mac is generated. You can set the container's mac address
|
||||
explicitly by providing a mac via the `--mac-address` parameter (format:
|
||||
12:34:56:78:9a:bc).
|
||||
By default a random MAC is generated. You can set the container's MAC address
|
||||
explicitly by providing a MAC via the `--mac-address` parameter (format:
|
||||
`12:34:56:78:9a:bc`).
|
||||
|
||||
Supported networking modes are:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user