Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Enable TCP port 2375 for external connection to Docker

Enable TCP port 2375 for external connection to Docker

See this issue.
Docker best practise to Control and configure Docker with systemd.

  1. Create daemon.json file in /etc/docker:

     {"hosts": ["tcp://", "unix:///var/run/docker.sock"]}
  2. Add /etc/systemd/system/docker.service.d/override.conf

  3. Reload the systemd daemon:

     systemctl daemon-reload
  4. Restart docker:

     systemctl restart docker.service
Copy link

Worked like charm on centos 7 too. Was struggling to get this working since 2 days.

Steps followed:

  1. vi /usr/lib/systemd/system/docker.service

add the line below where you find ExecStart (under Service section):

  1. ExecStart=/usr/bin/dockerd -H tcp:// -H unix:///var/run/docker.sock

3. systemctl daemon-reload
4. systemctl restart docker.service

Copy link

valterm commented Dec 9, 2021

Can confirm it works both on arch and debian 11.

Copy link

rfay commented Dec 27, 2021

I was also unable to get it to work on Debian 11 without the workaround in (directly editing the docker.service file). It seems that on Debian 11, the docker.service.d/override.conf doesn't actually get read, so you just have to edit the docker.service.

I also used ExecStart=/usr/sbin/dockerd --containerd=/run/containerd/containerd.sock --tls=false to avoid the very strong and important complaints:

Binding to IP address without --tlsverify is insecure and gives root access on this machine to everyone who has access to your network. host="tcp://".
Binding to an IP address, even on localhost, can also give access to scripts run in a browser. Be safe out there! host="tcp://"
Binding to an IP address without --tlsverify is deprecated. Startup is intentionally being slowed down to show this message host="tcp://"
Please consider generating tls certificates with client validation to prevent exposing unauthenticated root access to your network host="tcp://"
You can override this by explicitly specifying '--tls=false' or '--tlsverify=false' host="tcp://"
Support for listening on TCP without authentication or explicit intent to run without authentication will be removed in the next release host="tcp://"

Copy link

I absolutely do not get this run with docker 20.10.12 and ubuntu 21.10

I tried to edit /usr/lib/systemd/system/docker.service or do it via systemctl edit docker.service
Every time when I add -H tcp:// or tcp:// the docker.service cannot start
I tried with -H unix, without, with --containerd and without.

ExecStart=/usr/bin/dockerd -H tcp:// -H unix:///var/run/docker.sock --containerd=/run/containerd/containerd.sock

Any suggestion how to solve it?

Copy link

check logs, journalctl -xe. The options overlap, remove the , means all interfaces.

Copy link

h4r5h1t commented Jan 28, 2022

Follow this:

NOTE: Just change the IP from to and its work fine for Ubuntu ( for selenium dynamic grid)

Copy link

I found that the docker daemon failed to start on reboot (only) with the approach described here. I never tracked down the source of the problem.

However, it did lead me to implement instead an alternative solution with socat:

exec socat -d TCP-LISTEN:2375,fork UNIX-CONNECT:/var/run/docker.sock


  • I used daemontools to launch this an keep it running (
  • You can protect the port with the range=... option to socat, or with IP tables or netfilter.

Copy link

Nakilon commented Apr 20, 2022

Does not work for Docker Desktop on Windows. It refuses bind to

Copy link

I was having an issue to connect from another machine, turns out it was a firewall issue.
to fix I did:
ufw allow 2375/tcp
ufw reload
hopefully this helps someone.

Copy link


Copy link

sithson commented May 19, 2022

👍 ✔️ 🙇‍♀️
I can also confirm this, very much GG @styblope, my rock star hero!1 :))))))


  • Linux Mint 20.3 Una x64
  • Docker version 20.10.16, build aa7e414
  • Docker Compose version v2.5.0

Copy link


Copy link

I need to run docker from external docker client but the docker server is containerized (no daemon)
is it aplicable ?

Copy link

I need to run docker from external docker client but the docker server is containerized (no daemon) is it aplicable ?

AFAIK, Docker will be run as daemon wherever you deploy it.

Copy link

webzakimbo commented Sep 28, 2022

Here's another way that worked for me:


 ExecStart=/usr/bin/dockerd --config-file /etc/docker/daemon.json


  "hosts": ["tcp://", "unix:///var/run/docker.sock"]

Copy link

Thanks! for me it required a reboot to work

Copy link

AbdelazizSharaf001 commented Dec 9, 2022

AFAIK, Docker will be run as daemon wherever you deploy it.

Docker in Docker has two versions

  • docker:latest daemond and host dependant
  • docker:dind web interface based (seems to be no daemon | or fully isolated from host)

I was testing docker, minikube, and K8s functionalities inside docker

The way I was able to do that without exec command is docker context

for me it was not a server or daemon problem, but a context one

This answer helped me connecting to remote docker client and docker in docker via contexts :

So now we have both exposing docker via tcp and connecting to docker via tcp in this thread..

Copy link

AbdelazizSharaf001 commented Dec 9, 2022

Another thing to think for is security

Is the exposed port with your methods are encrypted or not ?

docker:dind has two ports to expose

  • 2375 no encrypton - context do not require cert or key
  • 2376 encrypted - context require key pair to qualify connection

Is that encryption applicable with your methods ?

I think this is the part where we go inside docker:dind entry point file

so it should be this part

dockerd \
     --host="$dockerSocket" \
     --host=tcp:// \
     --tlsverify \
     --tlscacert "$DOCKER_TLS_CERTDIR/server/ca.pem" \
     --tlscert "$DOCKER_TLS_CERTDIR/server/cert.pem" \
     --tlskey "$DOCKER_TLS_CERTDIR/server/key.pem"

and @russellhoff : you are right

  • the daemon server is running but as an entrypoint and not a service (I miss understood)

Copy link

abel-delafuente commented Dec 29, 2022

When i try to build the image be means of the BuildImage command, i am getting the

Connect to [/] failed: Connection refused: no further information

Apparently Gradle does not make match with the WSL platform IP.

Copy link

thanks a lot

Copy link

KMMehr commented Jan 14, 2023

Great job

Copy link

@abel-delafuente tcp not http
you could also try to use a unix socket instead and test again to make sure if it's a docker behavior or a network restriction

Copy link

Great! It's working for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment