docker swarm some times register eth0 other eth1

[viest]

/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 02:42:0A:00:07:97
          inet addr:10.0.7.151  Bcast:10.0.7.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
          RX packets:835 errors:0 dropped:0 overruns:0 frame:0
          TX packets:817 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:473052 (461.9 KiB)  TX bytes:97115 (94.8 KiB)

eth1      Link encap:Ethernet  HWaddr 02:42:0A:FF:06:F7
          inet addr:10.255.6.247  Bcast:10.255.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
          RX packets:67 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9171 (8.9 KiB)  TX bytes:23480 (22.9 KiB)

eth2      Link encap:Ethernet  HWaddr 02:42:AC:12:00:04
          inet addr:172.18.0.4  Bcast:172.18.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

fabio output:

 [INFO] consul: Registered fabio as "fabio"
 [INFO] consul: Registered fabio with id "fabio-ba36cab4e60d-9998"
 [INFO] consul: Registered fabio with address "10.255.6.247"
 [INFO] consul: Registered fabio with tags ""

consul check

Service 'fabio' check
Output
Get http://[10.255.6.247]:9998/health: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

I'm gonna use the eth0 network. What am I supposed to do?

[aaronhurt]

You can set the registry.consul.register.addr explicitly.

# registry.consul.register.addr configures the address for the service registration.
#
# Fabio registers itself in consul with this host:port address.
# It must point to the UI/API endpoint configured by ui.addr and defaults to its
# value.
#
# The default is
#
# registry.consul.register.addr = :9998

[aaronhurt]

We could possibly introduce go-sockaddr parsing of the addresses to make that a bit more dynamic.

https://github.com/hashicorp/go-sockaddr

[viest]

@leprechau Before the container starts, I don't know about Ip.

[viest]

Or like consul -advertise={{ GetInterfaceIP "eth0" }}

[aaronhurt]

@viest that's what consul, nomad and other HashiCorp products use ... that's the go-sockaddr project.

[viest]

Yes, I'm looking forward to joining this feature.

[aaronhurt]

Would you be open to submitting a PR to handle go-sockaddr parsing of the various places ip:port strings are interpreted?

[viest]

Clusters rely on this feature.

[aaronhurt]

I created #653 to address this issue.

[viest]

It's so cool.

@magiconair @pschultz please merge master, thanks.

[aaronhurt]

@viest we're just waiting on a review.

[viest]

I need this new feature so much, in my cluster.

But I think the main line was the latest merger 7 days ago.