ERRO[...] could not resolve peer "<nil>": timed out resolving peer by querying the cluster

[herveleclerc]

Architecture
1 consul server IP : 10.2.0.7
Launched like this

docker run -d -p 8300:8300 -p 8301:8301 -p 8301:8301/udp -p 8302:8302  -p 8302:8302/udp     -p 8400:8400 -p 8500:8500 -p 53:53/udp  progrium/consul --server -bootstrap-expect 1

3 docker nodes

Client:
 Version:      1.9.0-dev
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   1529343
 Built:        Tue Oct  6 19:16:24 UTC 2015
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.9.0-dev
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   1529343
 Built:        Tue Oct  6 19:16:24 UTC 2015
 OS/Arch:      linux/amd64
 Experimental: true

First (10.2.0.4)

DOCKER_OPTS='
-H tcp://0.0.0.0:2376
-H unix:///var/run/docker.sock
--storage-driver aufs
--tlsverify
--tlscacert /etc/docker/ca.pem
--tlscert /etc/docker/server.pem
--tlskey /etc/docker/server-key.pem
--label com.docker.network.driver.overlay.bind_interface=eth0
--label provider=azure
--cluster-store=consul://10.2.0.7:8500
--cluster-advertise=10.2.0.4:2376
--default-network=overlay:multihost
--debug=true

Second (10.2.0.5)

DOCKER_OPTS='
-H tcp://0.0.0.0:2376
-H unix:///var/run/docker.sock
--storage-driver aufs
--tlsverify
--tlscacert /etc/docker/ca.pem
--tlscert /etc/docker/server.pem
--tlskey /etc/docker/server-key.pem
--label com.docker.network.driver.overlay.bind_interface=eth0
--label com.docker.network.driver.overlay.neighbor_ip=10.2.0.4
--label provider=azure
--cluster-store=consul://10.2.0.7:8500
--cluster-advertise=10.2.0.5:2376
--default-network=overlay:multihost
--debug=true

'

Third (10.2.0.6)

DOCKER_OPTS='
-H tcp://0.0.0.0:2376
-H unix:///var/run/docker.sock
--storage-driver aufs
--tlsverify
--tlscacert /etc/docker/ca.pem
--tlscert /etc/docker/server.pem
--tlskey /etc/docker/server-key.pem
--label com.docker.network.driver.overlay.bind_interface=eth0
--label com.docker.network.driver.overlay.neighbor_ip=10.2.0.4
--label provider=azure
--cluster-store=consul://10.2.0.7:8500
--cluster-advertise=10.2.0.6:2376
--default-network=overlay:multihost
--debug=true

'

Discovery is OK

When i try to do launch a simple container :

docker run -ti --rm --name deb1 debian

Got these errors

Received query name:peerlookup, payload:c3a4708f2ce9b7165f9cc8628ba5e3deecc2abe6f2c0286ee7e1281a1ec74255 <nil>
2015/10/09 08:37:42 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:42 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:42 [DEBUG] serf: messageQueryType: peerlookup

ERRO[0314] could not resolve peer "<nil>": timed out resolving peer by querying the cluster

Received query name:peerlookup, payload:c3a4708f2ce9b7165f9cc8628ba5e3deecc2abe6f2c0286ee7e1281a1ec74255 <nil>
2015/10/09 08:37:42 [DEBUG] memberlist: Responding to push/pull sync with: 10.2.0.4:56260
2015/10/09 08:37:42 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:43 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:43 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:43 [DEBUG] serf: messageQueryType: peerlookup
2015/10/09 08:37:43 [DEBUG] serf: messageQueryType: peerlookup

ERRO[0315] could not resolve peer "<nil>": timed out resolving peer by querying the cluster

[mavenugo]

@herveleclerc --default-network=overlay:multihost has been removed.
Pls create a network using docker network create -d overlay multihost and then make use of the network in docker run --net=multihost ...

[herveleclerc]

can't make it work with docker run --net=multihost

Error response from daemon: invalid --net: production

to make it works :
docker network create -d overlay production
on host 1 :
`docker service publish svc1.production.overlay``

docker run --publish-service svc1.production -ti --rm --name houlala debian

on host2
`docker service publish svc2.production.overlay docker run --publish-service svc2.production -ti --rm --name houhou debian``

in container svc2

ping svc1.production
PING svc1.production (172.21.0.1): 56 data bytes
64 bytes from 172.21.0.1: icmp_seq=0 ttl=64 time=2.566 ms
64 bytes from 172.21.0.1: icmp_seq=1 ttl=64 time=1.092 ms
64 bytes from 172.21.0.1: icmp_seq=2 ttl=64 time=1.901 ms
64 bytes from 172.21.0.1: icmp_seq=3 ttl=64 time=1.195 ms

I don't know why i can't use --net=network_previously_created

[herveleclerc]

and for information the error message is still present ERRO[2760] could not resolve peer "<nil>": timed out resolving peer by querying the cluster

[GordonTheTurtle]

@herveleclerc It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

• For a bug: do you still experience the issue with the latest version?
• For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to #1926