Skip to content

Commit

Permalink
Explain --net=host option usage
Browse files Browse the repository at this point in the history
Fixes docker#11630

Signed-off-by: Ankush Agarwal <[email protected]>
  • Loading branch information
ankushagarwal committed Mar 30, 2015
1 parent 924d503 commit ddd2761
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/sources/reference/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,13 @@ container. The container's hostname will match the hostname on the host
system. Publishing ports and linking to other containers will not work
when sharing the host's network stack.

Compared to the default `bridge` mode, the `host` mode gives *significantly*
better networking performance since it uses the host's native networking stack
wheras the bridge has to go through one level of virtualizaion through the
docker daemon. It is recommended to run containers in this mode when their
networking performance is critical, for example, a production Load Balancer
or a High Performance Web Server.

> **Note**: `--net="host"` gives the container full access to local system
> services such as D-bus and is therefore considered insecure.
Expand Down

0 comments on commit ddd2761

Please sign in to comment.