Brand new docker compose deployment fails with Error response from daemon: Address already in use #3101
Replies: 1 comment
-
in my case, thanks to luis , the problem was discovered to be with the IP of the DNS server. Docker had reserver 192.168.1.1 for itself, then I used my pihole as DNS server and deployment completed. used 127.... 8.8... that didnt work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hyper v vm IP : 192.168.1.16
the traffic is expected to flow in this way:
Internet ---> firewall---> haproxy---> vm 192.168.1.16.
compose wont even start images complaining address is in use , which address is in use?
these are the ones currently open and listening on the machine oS:
netstat -putan
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:xx9 0.0.0.0:* LISTEN 768/sshd: /usr/sbin
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 696/systemd-resolve
tcp 0 464 192.168.1.16:xx9 192.168.1.154:62424 ESTABLISHED 1243/sshd: carlos [
tcp6 0 0 :::xx9 :::* LISTEN 768/sshd: /usr/sbin
udp 0 0 127.0.0.53:53 0.0.0.0:* 696/systemd-resolve
Env and compose attached. What I am doing wrong or what should I use instead? thanks!
compose.pdf
env.pdf
Beta Was this translation helpful? Give feedback.
All reactions