Port conflict issue

[crazybrad]

@girish Ran into an installation error after allowing the default port selections:

An error occurred during the install operation: Docker Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint 081ea546-42d2-43b3-8f87-0e27dec7d643 (06966450f28f844cdfb93632f6f00c811cbe180d1504ab7c67288971b6d3fa25): failed to bind port 0.0.0.0:40028/tcp: listen tcp4 0.0.0.0:40028: bind: address already in use

Attempting a re-install did not work.

[BrutalBirdie]

@crazybrad for some reason Port 40028 is already used from your server.
You can adjust the port range int he install, or even better, you should investigate why this port is used it should not be used.

[crazybrad]

@BrutalBirdie It looks like a docker container is using those ports:

dockerd 1130 root 324u IPv4 8340333 0t0 TCP *:40028 (LISTEN)
dockerd 1130 root 325u IPv6 8340334 0t0 TCP *:40028 (LISTEN)

And here are the details of PID 1130:

─1130 /usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --userland-pro>

Any ideas?

[BrutalBirdie]

@crazybrad No idea
But you can just adjust the port range from 40000 to 40100 then 40100 to 40201 will be used.

[joseph]

I think this is some docker issue. We see the same issue in our CI and also reported in the Mirotalk threads. Reinstalling fixes the problem as you already found out