[BUG] Default config prevents subsequent launches on Windows

[tsvl]

Describe the bug
If no existing config.toml is found, Oxker creates a new one on first run with host = "/var/run/docker.sock", which causes it to be unable to connect to the Docker daemon on subsequent runs on Windows systems until the config is manually edited (removing the host line entirely seems to work fine for me) or deleted.
To Reproduce
Steps to reproduce the behavior:

1. Launch Oxker on a Windows system where no config.toml exists.
2. Observe that a new config.toml is created with host = "/var/run/docker.sock".
3. Close and relaunch Oxker, it will fail to connect to the Docker daemon.
4. Delete the config.toml file or edit it to remove the host line.
5. Relaunch Oxker, it should now connect successfully again.

Expected behavior
Oxker should either not set a default host in the config.toml on Windows systems, or it should set it to a value that allows successful connection to the Docker daemon on Windows.

Desktop (please complete the following information):

• OS: Windows 11 26220.6982

[mrjackwills]

Thanks, huge oversight on my part there, I stopped actually testing on Windows a while back.

What should the Windows Docker host value actually be?

If I make a fixed Windows binary, and post it in here, would you be able to check it? It'll then get rolled into the next release, which will be soon - I tend to follow the six week Rust release cycle.