ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
James Nugent 2016-09-21 09:30:50 +01:00
parent 1b6c1cccf3
commit c942707476
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/docs/providers/docker/index.html.markdown
View File

@ -57,4 +57,10 @@ The following arguments are supported:
for connecting to the Docker host via TLS. If this is blank, the for connecting to the Docker host via TLS. If this is blank, the
`DOCKER_CERT_PATH` will also be checked. `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 <machine-name>)` prior
to running Terraform, and the host and certificate path will be extracted from
the environment.