Arch Linux

hendry

Member

From: Singapore

Registered: 2009-09-08

Posts: 157

Website

zeroconf binds to wrong IP when Docker is running

I configured a service to listen to gem.local and I noticed that it stopped working. On a closer look it looks it's binding to the wrong IP. Instead of 10.8.1.113 it's binding to the Docker IP of 172.17.0.1.

Any ideas how I fix this?

gem:~$ ping gem.local
PING gem.local (172.17.0.1) 56(84) bytes of data.
64 bytes from gem (172.17.0.1): icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from gem (172.17.0.1): icmp_seq=2 ttl=64 time=0.124 ms
^C
--- gem.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.086/0.105/0.124/0.019 ms
gem:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether c0:3f:d5:6c:1e:43 brd ff:ff:ff:ff:ff:ff
    inet 10.8.1.113/24 brd 10.8.1.255 scope global dynamic enp3s0
       valid_lft 436sec preferred_lft 436sec
    inet6 fe80::c23f:d5ff:fe6c:1e43/64 scope link
       valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:a8:cd:31:f9:57 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:9f:ba:06:95 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever

BONUS points: Anyone know how to bind several .local addresses to one IP? E.g. foo.local, bar.local binding to my enp3s0's IP.