Works only with the default docker context

[domust]

Hi, neat project!

It would be nice if dot would be able to detect the current docker context instead of assuming it's always the default one.

[cvhariharan]

Hi, thanks for opening this issue.

Docker client is initialized using FromEnv https://github.com/opnlabs/dot/blob/master/pkg/runner/docker.go#L146 so it can be customized using env variables.

Is this what you are referring to? Let me know if you were referring to something else.

[domust]

I was referring to:

docker context ls | grep default
default      Current DOCKER_HOST based configuration   unix:///var/run/docker.sock

I'm not using the default docker context, which means that the unix socket the client uses to reach the daemon is in a different location and thus dot is not able to run. Setting environment variable changes the socket location of the default context, meaning that now I have 2 contexts with identical socket locations, which defeats the purpose of having multiple contexts. I would have expected dot to detect the currently selected context and use its socket instead of the default one.

[cvhariharan]

client.FromEnv option should take care of this. If the DOCKER_HOST environment variable is set, dot will use that when creating the client.