Welcome to Nick's Random Musings

Of course I don't know what I'm doing, what fun would that be?


Docker Cannot bind to port


meta
Nick Gully

If docker is complaining about containers that cannot bind to ports, and you do not have other processes running on those ports, it may be that systemd has a bad ExecStart for docker, and it broke sub-process access.

It could look like: exec: "docker-proxy": executable file not found in $PATH

Or is could be: level=debug msg="FIXME: Got an API for which error does not match any expected type!!!: driver failed programming external connectivity on endpoint my-funny-valentine (43dc047fd585ce93dc8230d0ab60a8dfd3c5bef77b4055d218ed6722b416fd1d): Bind for 0.0.0.0:9092 failed: port is already allocated" error_type=types.internal module=api

Change this: systemd/system/docker.service.d/hosts.conf 2:ExecStart= 3:ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2736

To this: override.conf [Service] ExecStart= ExecStart=/usr/bin/dockerd [ngully@magpie docker.service.d]$ pwd /etc/systemd/system/docker.service.d

This was on Fedora 31, docker "moby-engine"

A whale of a good time.