Ducker should respect the DOCKER_HOST environment variable

[danyshs]

Describe the bug
Installed Ducker, and tried to run it, but can't debug why it's throwing an error because it's throwing multiple and doesn't point towards a valid file

To Reproduce
Steps to reproduce the behavior:

1. Install Ducker
2. Try to run it
3. Location where the error points to while being thrown doesn't exist

Expected behavior
Ideally it should just work, but at least it should throw an error that points to a valid directory

Screenshots

Desktop (please complete the following information):

• OS: WSL2 - Arch Linux (Base; Windows 11)
• Version 5.15.153.1-microsoft-standard-WSL2

[robertpsoane]

@danyshs this seems to be a config issue

The error is essentially a prettified stack trace, and it should be read as
"Error - 0: ... because 1:... because ...", with the location referencing the location of line in the source code that's raised the error

Ducker is unable to find the docker socket file (usually unix:///var/run/docker.sock)

Does that file exist? If it does, what happens if you execute docker image ls?

[katertier]

I'm in the same boat albeit on Mac with Colima which insists to put its docker.sock into ~/.colima/ to not interfere with Docker Desktop.

@danyshs: did you enable WSL2 integration in Docker Desktop? Check your DOCKER_HOST environment variable and add it as parameter when using ducker (-d), or create a config file with -e and update it.

@robertpsoane: ducker seems to ignore DOCKER_HOST, maybe add reading it in a future version (at least for local files)?

[danyshs]

[I have Docker-cli on wsl, I don't have Docker Desktop!]

I..............think I realized what the issue was.
At the time of making the post, I think the docker daemon was off.

All is well now.

[danyshs]

Either that, or when I had no containers or images loaded up, it had a breaking error rather than launching to an empty screen.
That is a possibility too.