kotovalexarian-likes-github
/
moby--moby
mirror of https://github.com/moby/moby.git
1
0
Fork 0
Code Releases Activity

Modify ip_forward instructions 

Signed-off-by: ChristoperBiscardi <chris@docker.com>
This commit is contained in:
ChristoperBiscardi 2015-03-10 19:28:55 -07:00
parent 79a0fa29f1
commit 4ab18fa2ac
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/sources/articles/networking.md
View File

@ -228,11 +228,11 @@ Whether a container can talk to the world is governed by two factors.
Docker will go set `ip_forward` to `1` for you when the server Docker will go set `ip_forward` to `1` for you when the server
starts up. To check the setting or turn it on manually: starts up. To check the setting or turn it on manually:
$ cat /proc/sys/net/ipv4/ip_forward $ sysctl net.ipv4.conf.all.forwarding
0 net.ipv4.conf.all.forwarding = 0
$ echo 1 > /proc/sys/net/ipv4/ip_forward $ sysctl net.ipv4.conf.all.forwarding=1
$ cat /proc/sys/net/ipv4/ip_forward $ sysctl net.ipv4.conf.all.forwarding
1 net.ipv4.conf.all.forwarding = 1
Many using Docker will want `ip_forward` to be on, to at Many using Docker will want `ip_forward` to be on, to at
least make communication *possible* between containers and least make communication *possible* between containers and