gliderlabs / gliderlabs/docker-consul

Node is seen in active state even my docker daemon is not running.

Open
#69 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
1.1k
Forks
270
PR merge metrics
No merged PRs in 30d

Description

I 've 2 hosts where I 've docker running. Consul is also running on a docker container.

[root@docker2 ~]#docker exec -it 7e74638cb211 consul members
Node Address Status Type Build Protocol
node1 172.16.131.253:8301 alive server 0.5.0 2
node2 172.16.131.252:8301 alive server 0.5.0 2

I shows both my node as alive whereas my node2 is not even running docker at the moment. Docker on this node actually kind of crashed by consul is not able to detect that.

[root@docker1 ~]# docker ps
FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

Please suggest.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.