From 6148a6ae030d89de9e575af4dde826488dba466d Mon Sep 17 00:00:00 2001 From: ChristoperBiscardi Date: Tue, 10 Mar 2015 19:28:55 -0700 Subject: [PATCH] Modify ip_forward instructions Signed-off-by: ChristoperBiscardi Upstream-commit: 4ab18fa2ac119c26516f2156dabda9dd0a781301 Component: engine --- components/engine/docs/sources/articles/networking.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/components/engine/docs/sources/articles/networking.md b/components/engine/docs/sources/articles/networking.md index 102155b319..e4471dc745 100644 --- a/components/engine/docs/sources/articles/networking.md +++ b/components/engine/docs/sources/articles/networking.md @@ -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