Add an option to disable IP masquerading
For the cases where --bip option is used it is sometimes best to disable
IP masquerading as the provided bridge IP range may be routable.
Signed-off-by: Eugene Yakubovich <eugene.yakubovich@coreos.com>
Upstream-commit: a492b97cd0
Component: cli
This commit is contained in:
committed by
Tibor Vass
parent
409eb6c388
commit
ff2b882022
@ -67,6 +67,7 @@ expect an integer, and they can only be specified once.
|
||||
--icc=true Enable inter-container communication
|
||||
--ip=0.0.0.0 Default IP address to use when binding container ports
|
||||
--ip-forward=true Enable net.ipv4.ip_forward
|
||||
--ip-masq=true Enable IP masquerading for bridge's IP range.
|
||||
--iptables=true Enable Docker's addition of iptables rules
|
||||
--mtu=0 Set the containers network MTU
|
||||
if no value is provided: default to the default route MTU or 1500 if no default route is available
|
||||
@ -110,6 +111,10 @@ the `-H` flag for the client.
|
||||
$ sudo docker ps
|
||||
# both are equal
|
||||
|
||||
IP masquerading uses address translation to allow containers without a public IP to talk
|
||||
to other machines on the Internet. This may interfere with some network topologies and
|
||||
can be disabled with --ip-masq=false.
|
||||
|
||||
To run the daemon with [systemd socket activation](
|
||||
http://0pointer.de/blog/projects/socket-activation.html), use
|
||||
`docker -d -H fd://`. Using `fd://` will work perfectly for most setups but
|
||||
|
||||
Reference in New Issue
Block a user