See this issue.
Docker best practise to Control and configure Docker with systemd.
Create daemon.json file in /etc/docker:
{"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}
Add /etc/systemd/system/docker.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd
Reload the systemd daemon:
systemctl daemon-reload
Restart docker:
systemctl restart docker.service
i had to do the following:
$ cat /etc/systemd/system/docker.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/sbin/dockerd --config-file /etc/docker/daemon.overrided.json
$ cat /etc/docker/daemon.overrided.json
{
"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]
}
The binary is in /usr/sbin/dockerd, and changing the daemon.json conflicted with the default parameter -H fd://
for ubuntu /etc/systemd/system/docker.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd --containerd=/run/containerd/containerd.sock
Thanks!
For Raspberry Pi bookworm it is
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock -H tcp://0.0.0.0:2375
without the daemon.json
Exposing the docker daemon on 0.0.0.0 especially on something which faces the internet is a TERRIBLE idea!
It's literally like giving everyone sudo access...
Bind to 127.0.0.1 and portforward.
You don't even have to, the docker client can speak ssh) via:
DOCKER_HOST=“ssh://user@remotehost