From ae1f0ec380782c14a87ac22757473b00f61204e3 Mon Sep 17 00:00:00 2001 From: Alexandre Figura Date: Tue, 4 Dec 2018 22:23:07 +0100 Subject: [PATCH] Change TLS args in Docker configuration example The TLS args given in this example were misleading, because they were preventing the Docker daemon to listen on the port 2376 (even if the daemon still succeeds to start...). The reason is very simple: when using `sudo ros tls gen --server ...`, the server and CA certificates will be stored in `/etc/docker/tls`. But their paths were given as relative paths, and not absolute paths, in the previous example. --- .../os/v1.x/en/installation/configuration/docker/_index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/os/v1.x/en/installation/configuration/docker/_index.md b/content/os/v1.x/en/installation/configuration/docker/_index.md index 1dbd9c3e21a..db7f03c56f1 100644 --- a/content/os/v1.x/en/installation/configuration/docker/_index.md +++ b/content/os/v1.x/en/installation/configuration/docker/_index.md @@ -14,7 +14,12 @@ In your cloud-config, Docker configuration is located under the `rancher.docker` rancher: docker: tls: true - tls_args: [--tlsverify, --tlscacert=ca.pem, --tlscert=server-cert.pem, --tlskey=server-key.pem, '-H=0.0.0.0:2376'] + tls_args: + - "--tlsverify" + - "--tlscacert=/etc/docker/tls/ca.pem" + - "--tlscert=/etc/docker/tls/server-cert.pem" + - "--tlskey=/etc/docker/tls/server-key.pem" + - "-H=0.0.0.0:2376" storage_driver: overlay ```