Browse code

Clarify that ipmasq rules are not added when iptables is false

Signed-off-by: Misty Stanley-Jones <misty@docker.com>

bbayani authored on 2016/11/19 07:22:49
Showing 1 changed files
... ...
@@ -1336,10 +1336,14 @@ set this parameter separately for each daemon.
1336 1336
 - `-p, --pidfile=/var/run/docker.pid` is the path where the process ID of the daemon is stored. Specify the path for your
1337 1337
 pid file here.
1338 1338
 - `--host=[]` specifies where the Docker daemon will listen for client connections. If unspecified, it defaults to `/var/run/docker.sock`.
1339
-- `--iptables=false` prevents the Docker daemon from adding iptables rules. If
1340
-  multiple daemons manage iptables rules, they may overwrite rules set by
1341
-  another daemon. Be aware that disabling this option requires you to manually
1342
-  add iptables rules to expose container ports.
1339
+-  `--iptables=false` prevents the Docker daemon from adding iptables rules. If
1340
+multiple daemons manage iptables rules, they may overwrite rules set by another
1341
+daemon. Be aware that disabling this option requires you to manually add
1342
+iptables rules to expose container ports. If you prevent Docker from adding
1343
+iptables rules, Docker will also not add IP masquerading rules, even if you set
1344
+`--ip-masq` to `true`. Without IP masquerading rules, Docker containers will not be
1345
+able to connect to external hosts or the internet when using network other than
1346
+default bridge.
1343 1347
 - `--config-file=/etc/docker/daemon.json` is the path where configuration file is stored. You can use it instead of
1344 1348
 daemon flags. Specify the path for each daemon.
1345 1349
 - `--tls*` Docker daemon supports `--tlsverify` mode that enforces encrypted and authenticated remote connections.