p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Modify ip_forward instructions

Browse Source 
Signed-off-by: ChristoperBiscardi <chris@docker.com>
Upstream-commit: 4ab18fa2ac119c26516f2156dabda9dd0a781301
Component: engine
This commit is contained in:
ChristoperBiscardi
2015-03-10 19:28:55 -07:00
parent 6d6d8eee07
commit 6148a6ae03
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
components/engine/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
starts up. To check the setting or turn it on manually:
$ cat /proc/sys/net/ipv4/ip_forward
0
$ echo 1 > /proc/sys/net/ipv4/ip_forward
$ cat /proc/sys/net/ipv4/ip_forward
1
$ sysctl net.ipv4.conf.all.forwarding
net.ipv4.conf.all.forwarding = 0
$ sysctl net.ipv4.conf.all.forwarding=1
$ sysctl net.ipv4.conf.all.forwarding
net.ipv4.conf.all.forwarding = 1
Many using Docker will want `ip_forward` to be on, to at
least make communication *possible* between containers and