From e1ba892827600402c34862696b7af2c29719550d Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Sat, 6 Jun 2015 23:54:46 +0100 Subject: [PATCH] go back to using the tcp:// prefix in DOCKER_HOST seems to be the recommended way --- site/proxy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/site/proxy.md b/site/proxy.md index bab4b601..b95f3d74 100644 --- a/site/proxy.md +++ b/site/proxy.md @@ -42,7 +42,7 @@ can adjust the connection to docker via the `-H` argument. All docker commands can be run via the proxy, so it is safe to globally adjust your `DOCKER_HOST`, e.g. - host1$ export DOCKER_HOST=localhost:12375 + host1$ export DOCKER_HOST=tcp://localhost:12375 host1$ docker ps ... @@ -130,12 +130,12 @@ to point at the latter: host1$ weave launch -iprange 10.2.3.0/24 host1$ weave launch-dns 10.2.4.1/24 host1$ weave launch-proxy --with-ipam --with-dns - host1$ export DOCKER_HOST=localhost:12375 + host1$ export DOCKER_HOST=tcp://localhost:12375 host2$ weave launch -iprange 10.2.3.0/24 host1 host2$ weave launch-dns 10.2.4.2/24 host2$ weave launch-proxy --with-ipam --with-dns - host2$ export DOCKER_HOST=localhost:12375 + host2$ export DOCKER_HOST=tcp://localhost:12375 NB: Note that the two weaveDNS instances must be given unique IPs, on a subnet different from that used for IP allocation.