Add non default docker daemon path support

[Laur1nMartins]

Looks promising!

But is there a way to set the docker daemon path if it is non standard?

I run my docker in user mode which is why I have a different path to the daemon. With a Quick Look into the code I could not find out if it is possible to change it via the config.

I could create a pull request once I tested it and you tell me where I should change that value.

[ajayd-san]

Hey!

I need some more info.

By user mode, do you mean non-root mode? Or you have installed the daemon in a different path?

I tried searching up the latter but couldn't find much info about it.

Also, is this on windows ?

[Spaider]

Of course, I might be wrong, but it looks like the point is to support different docker contexts. That ones use see when you type docker context ls.

For now, it seems that gmd defaults to unix:///var/run/docker.sock though it may very well not be the default context.

[ajayd-san]

Thats valid, I could add support for custom contexts in the next release. Thanks for your input!!!

[benniekiss]

Allowing connections to remote sockets would also be really helpful, either over tcp or ssh. I don't know about docker, but for podman, the bindings offer a method to do remote connections

[ajayd-san]

@benniekiss I might be able to add that with podman support in the next release 👀

[Abdul-0x4A]

Had the same issue using docker with colima. I'm on darwin and used nix to install everything, though I notice it's only on version 1.4 there. Anyway I've found two workarounds that work for me:

• Create a symlink to the default location
  • E.g. sudo ln -sf $HOME/.config/colima/default/docker.sock /var/run/docker.sock
• Set the DOCKER_HOST env var to unix://${HOME}/.config/colima/default/docker.sock

I believe If you didn't use nix to install stuff your socket might live in {$HOME}/.colima/default