Docker installation Error: address already in use

hobiga

I’m trying to deploy a fresh installation of mailcow via docker compose. When I attempt do run the docker compose up -d I"m getting the following error:

Error response from daemon: driver failed programming external connectivity on endpoint mailcowdockerized-dovecot-mailcow-1 (153fa5667f858c8bd8891aacbfbb1fdfa23aca7897500b11e5847f74e21a92fd): Error starting userland proxy: listen tcp4 0.0.0.0:995: bind: address already in use

What is strange is that I have no services already running on that port. I’ve validated using both ss and netstat.

ss -aultnp|grep 995
netstat -tulpn |grep 995

Both return no results.

I’ve read a post where there was some ip conflict with the address of 172.22.1.250 being already assigned and the dovecot container was unable to use that ip. I ran the following command which also didn’t return anything.

docker network inspect mailcowdockerized_mailcow-network | grep 172.22.1.250

In fact when I run just the docker network inspect mailcowdockerized_mailcow-network I don’t see the dovecot container listed at all. Not sure if I should.

Anyone ran into this kind of issue in the past? Not sure what else to try at this point.

Thanks

D4niel

docker network inspect mailcowdockerized_mailcow-network | grep 172.22.1.250

You’d probably have to check all docker networks, not just the mailcow one.

In fact when I run just the docker network inspect mailcowdockerized_mailcow-network I don’t see the dovecot container listed at all. Not sure if I should.

It won’t start when the address is in use.

hobiga

Thanks for the thought. I ran this command to check all my ip’s:

docker network inspect $(docker network ls -q)|grep -E “IPv(4)A”

            "IPv4Address": "172.21.0.2/16",
            "IPv4Address": "172.18.0.2/16",
            "IPv4Address": "192.168.100.21/24",
            "IPv4Address": "192.168.100.25/24",
            "IPv4Address": "172.22.1.8/24",
            "IPv4Address": "172.22.1.11/24",
            "IPv4Address": "172.22.1.248/24",
            "IPv4Address": "172.22.1.9/24",
            "IPv4Address": "172.22.1.253/24",
            "IPv4Address": "172.22.1.7/24",
            "IPv4Address": "172.22.1.5/24",
            "IPv4Address": "172.22.1.249/24",
            "IPv4Address": "172.22.1.254/24",
            "IPv4Address": "172.22.1.2/24",
            "IPv4Address": "172.22.1.4/24",
            "IPv4Address": "172.22.1.3/24",
            "IPv4Address": "172.22.1.6/24",

No conflicts in any of the other docker networks from the looks of it.