How to expose Rancher-Desktop docker daemon on tcp://0.0.0.0:2375

[abcarcol]

I have already created a configuration file at /etc/docker/daemon.json with the following content:

{
"hosts": [
"tcp://0.0.0.0:2375"
]
}

However, this is in conflict with the parameters used in the command line, as shown in the error below:

unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives are specified both as a flag and in the configuration file: hosts: (from flag: [unix:///mnt/wsl/rancher-desktop/run/docker.sock unix:///var/run/docker.sock], from file: [tcp://0.0.0.0:2375])
Error: timed out waiting for /mnt/wsl/rancher-desktop/run/docker.sock to exist
Usage:
wsl-helper docker-proxy start [flags]

Flags:
--endpoint string Dockerd socket endpoint (default "/mnt/wsl/rancher-desktop/run/docker.sock")
-h, --help help for start
--port uint32 Vsock port to listen on (default 23752375)

Global Flags:
--verbose count enable extra logging

How can I restart the docker daemon in the Rancher-Desktop WSL2 distro to use the daemon.json config instead of the mentioned flags?.

Many thanks in advance,
Abel.

[jandubois]

I've created enhancement request #2851 from this question; I don't think this is currently possible.

[dermot-hardy]

I'm running this to workaround the problem:

docker container run -dt --name expose-docker-on-2375 --network=host -v /var/run/docker.sock:/var/run/docker.sock --restart=always rancher/socat-docker

It seems to work quite well.

[jiri-otoupal]

It does not work for me:
docker: error during connect: Post "http://localhost:2375/v1.24/containers/create?name=expose-docker-on-2375": dial tcp [::1]:2375: connectex: No connection could be made because the target machine actively refused it.

[dermot-hardy]

Run wsl -d rancher-desktop first, so that you're running it from within the Rancher Desktop distribution.

[mung3r]

When I test within rancher-desktop distro, it works. From powershell (or the host side) it still seems like it's not exposed or blocked.

[mung3r]

This works for me now. There was some other windows process that was using port 2375. Once I sorted that out, I was able to test successfully from the host side.

[MrBuddyCasino]

Yeah this is annoying. I'm using Testcontainers and it can't talk to a remote Rancher Desktop, because docker-java does not support the ssh transport, which could work around this.

It is also possible to bind to all network interfaces, not just 127.0.0.1:

docker run -d --restart=always \
    -p 0.0.0.0:2375:2375 \
    -v /var/run/docker.sock:/var/run/docker.sock \
    alpine/socat \
    tcp-listen:2375,fork,reuseaddr unix-connect:/var/run/docker.sock