kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Add NETWORK_NAME_or_ID value for --net= option

Browse source 
Signed-off-by: Wen Cheng Ma <wenchma@cn.ibm.com>
This commit is contained in:
Wen Cheng Ma 2015-11-30 16:28:54 +08:00
parent db6c4c99d8
commit 08328cb703
7 changed files with 33 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/userguide/networking/default_network/container-basics.md
View file

@ -15,7 +15,7 @@ DRAFT to prevent building. Keeping for one cycle before deleting.
# How the default network
The information in this section explains configuring container DNS within tthe Docker default bridge. This is a `bridge` network named `bridge` created
The information in this section explains configuring container networks within the Docker default bridge. This is a `bridge` network named `bridge` created
automatically when you install Docker.
**Note**: The [Docker networks feature](../dockernetworks.md) allows you to create user-defined networks in addition to the default bridge network.
@ -40,7 +40,7 @@ The steps with which Docker configures a container are:
With these steps complete, the container now possesses an `eth0` (virtual) network card and will find itself able to communicate with other containers and the rest of the Internet.
You can opt out of the above process for a particular container by giving the `--net=` option to `docker run`, which takes four possible values.
You can opt out of the above process for a particular container by giving the `--net=` option to `docker run`, which takes these possible values.
- `--net=bridge` -- The default action, that connects the container to the Docker bridge as described above.
- `--net=host` -- Tells Docker to skip placing the container inside of a separate network stack. In essence, this choice tells Docker to **not containerize the container's networking**! While container processes will still be confined to their own filesystem and process list and resource limits, a quick `ip addr` command will show you that, network-wise, they live "outside" in the main Docker host and have full access to its network interfaces. Note that this does **not** let the container reconfigure the host network stack -- that would require `--privileged=true` -- but it does let container processes open low-numbered ports like any other root process. It also allows the container to access local network services like D-bus. This can lead to processes in the container being able to do unexpected things like [restart your computer](https://github.com/docker/docker/issues/6401). You should use this option with caution.
@ -49,6 +49,8 @@ You can opt out of the above process for a particular container by giving the `-
- `--net=none` -- Tells Docker to put the container inside of its own network stack but not to take any steps to configure its network, leaving you free to build any of the custom configurations explored in the last few sections of this document.
- `--net=<network-name>|<network-id>` -- Tells Docker to connect the container to a user-defined network.
## Manually network
To get an idea of the steps that are necessary if you use `--net=none` as described in that last bullet point, here are the commands that you would run to reach roughly the same configuration as if you had let Docker do all of the configuration: