From 9263d3e82c7bfc4a04e5cbf16de723ed6fb75a55 Mon Sep 17 00:00:00 2001 From: Adam Harrison Date: Wed, 18 Nov 2015 10:24:46 +0000 Subject: [PATCH] Fix erroneously hyphenated Docker TLS arguments --- site/proxy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site/proxy.md b/site/proxy.md index acf3a3798a..c34fbe3059 100644 --- a/site/proxy.md +++ b/site/proxy.md @@ -237,8 +237,8 @@ supplied to the docker daemon. For example, if you have generated your certificates and keys into the docker host's `/tls` directory, we can launch the proxy with: - host1$ weave launch-proxy --tls-verify --tls-cacert=/tls/ca.pem \ - --tls-cert=/tls/server-cert.pem --tls-key=/tls/server-key.pem + host1$ weave launch-proxy --tlsverify --tlscacert=/tls/ca.pem \ + --tlscert=/tls/server-cert.pem --tlskey=/tls/server-key.pem The paths to your certificates and key must be provided as absolute paths which exist on the docker host. @@ -254,8 +254,8 @@ for an example. With the proxy running over TLS, we can configure our regular docker client to use TLS on a per-invocation basis with - $ docker --tls-verify --tls-cacert=ca.pem --tls-cert=cert.pem \ - --tls-key=key.pem -H=tcp://host1:12375 version + $ docker --tlsverify --tlscacert=ca.pem --tlscert=cert.pem \ + --tlskey=key.pem -H=tcp://host1:12375 version ... or,