From c94270747604b6d635c9be3565c0a2fa76db8a16 Mon Sep 17 00:00:00 2001 From: James Nugent Date: Wed, 21 Sep 2016 09:30:50 +0100 Subject: [PATCH] provider/docker: Add alternative to cert_path Add a note about using `eval $(docker-machine env)` when using Docker Machine to avoid having to hard code a certificate path. --- website/source/docs/providers/docker/index.html.markdown | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/website/source/docs/providers/docker/index.html.markdown b/website/source/docs/providers/docker/index.html.markdown index 1cf883dd9..1b92cb1b7 100644 --- a/website/source/docs/providers/docker/index.html.markdown +++ b/website/source/docs/providers/docker/index.html.markdown @@ -57,4 +57,10 @@ The following arguments are supported: for connecting to the Docker host via TLS. If this is blank, the `DOCKER_CERT_PATH` will also be checked. -Note: As per [Docker Remote API documentation](https://docs.docker.com/engine/reference/api/docker_remote_api/), in any docker-machine environment, the Docker daemon uses an encrypted TCP socket (TLS) and requires `cert_path` for a successful connection. +~> **NOTE on Certificates and `docker-machine`:** As per [Docker Remote API +documentation](https://docs.docker.com/engine/reference/api/docker_remote_api/), +in any docker-machine environment, the Docker daemon uses an encrypted TCP +socket (TLS) and requires `cert_path` for a successful connection. As an alternative, +if using `docker-machine`, run `eval $(docker-machine env )` prior +to running Terraform, and the host and certificate path will be extracted from +the environment.