Connect to a Docker daemon on TCP about caddy-docker-proxy HOT 6 CLOSED

Thanks for reviewing @ibnesayeed .

We're using the function NewEnvClient from docker. It creates a docker client using Environment variables configuration falling back to default values.

I think you can configure how it should connect to the docker api by setting environment variables.

// Use DOCKER_HOST to set the url to the docker server.
// Use DOCKER_API_VERSION to set the version of the API to reach, leave empty for latest.
// Use DOCKER_CERT_PATH to load the tls certificates from.
// Use DOCKER_TLS_VERIFY to enable or disable TLS verification, off by default.

More info here: https://github.com/docker/engine-api/blob/master/client/client.go#L42

from caddy-docker-proxy.

Yes, from my casual scan of your code, I did not see any place where you were opening the socket file yourself, so I knew it was offloaded to Docker packages. This means we get this functionality for free. We just need to test it and document accordingly.

from caddy-docker-proxy.

Added that information to README file.

from caddy-docker-proxy.

@lucaslorentz, I think where we are documenting the DOCKER_HOST, we need to explicitly mention that by default it will connect to /var/run/docker.sock socket file.

from caddy-docker-proxy.

DOCKER_HOST default value varies per platform /var/run/docker.sock
Windows: "npipe:////./pipe/docker_engine"
Unix: "unix:///var/run/docker.sock"

I will add it to README.

from caddy-docker-proxy.

Done

from caddy-docker-proxy.