From 52509087a7154bb6bcceae82c3b00e23873f97c6 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Sat, 6 Jun 2015 16:19:44 +0100 Subject: [PATCH] cosmetic --- site/proxy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site/proxy.md b/site/proxy.md index 9712b288..a80a7db1 100644 --- a/site/proxy.md +++ b/site/proxy.md @@ -129,10 +129,10 @@ paths which exist on the docker host. Because the proxy connects to the docker daemon at `unix:///var/run/docker.sock`, you must ensure that the daemon is listening there. To do this, you will need to pass the `-H -unix:///var/run/docker.sock` option when starting the docker daemon, in -addition to the `-H` options for configuring the TCP listener. See -[the Docker -documentation](https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket) for an example. +unix:///var/run/docker.sock` option when starting the docker daemon, +in addition to the `-H` options for configuring the TCP listener. See +[the Docker documentation](https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket) +for an example. With the proxy running over TLS, we can configure our regular docker client