When Docker Swarm discovery is file, how should the cluster be created?

Manage: 192.168.5.5

Node: 192.168.5.3 , 192.168.5.4

Docker Swarm discovery is file://path/to/file

Cluster file content:

 192.168.5.3:2375 192.168.5.4:2375 

Manage (192.168.5.5) command:
docker run -d -it -h node-m --name=node-m --restart=always -v $(pwd)/cluster:/tmp/cluster -p 3375:3375 swarm manage -H 0.0.0.0:3375 file:///tmp/cluster

Node1 (192.168.5.3) command:
docker run -d -it -h node-1 --name=node-1 -v $(pwd)/cluster:/tmp/cluster swarm join --addr=192.168.5.3:2375 file:///tmp/cluster

Node2 (92.168.5.4) command:
docker run -d -it -h node-2 --name=node-2 -v $(pwd)/cluster:/tmp/cluster swarm join --addr=192.168.5.4:2375 file:///tmp/cluster


Manage (192.168.5.5) command:

 [root@manage opt]# docker run --rm -v $(pwd)/cluster:/tmp/cluster swarm list file:///tmp/cluster 192.168.5.3:2375 192.168.5.4:2375 [root@manage opt]# docker -H 0.0.0.0:3375 info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: swarm/1.2.6 Role: primary Strategy: spread Filters: health, port, containerslots, dependency, affinity, constraint, whitelist Nodes: 2 (unknown): 192.168.5.3:2375 └ ID: └ Status: Pending └ Containers: 0 └ Reserved CPUs: 0 / 0 └ Reserved Memory: 0 B / 0 B └ Labels: └ Error: Cannot connect to the Docker daemon at tcp://192.168.5.3:2375. Is the docker daemon running? └ UpdatedAt: 2017-04-10T19:03:37Z └ ServerVersion: (unknown): 192.168.5.4:2375 └ ID: └ Status: Pending └ Containers: 0 └ Reserved CPUs: 0 / 0 └ Reserved Memory: 0 B / 0 B └ Labels: └ Error: Cannot connect to the Docker daemon at tcp://192.168.5.4:2375. Is the docker daemon running? └ UpdatedAt: 2017-04-10T19:03:37Z └ ServerVersion: Plugins: Volume: Network: Swarm: NodeID: Is Manager: false Node Address: Security Options: Kernel Version: 3.10.0-514.el7.x86_64 Operating System: linux Architecture: amd64 Number of Docker Hooks: 2 CPUs: 0 Total Memory: 0 B Name: node-m Docker Root Dir: Debug Mode (client): false Debug Mode (server): false WARNING: No kernel memory limit support Registries: 

Manage, node1, node2 ps -a command results

 [root@manage opt]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 18a246b46399 swarm "/swarm manage -H 0.0" 3 minutes ago Up 3 minutes 2375/tcp, 0.0.0.0:3375->3375/tcp node-m [root@node1 opt]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES df43c2cbfee0 swarm "/swarm join --addr=1" 2 minutes ago Up 2 minutes 2375/tcp node-1 [root@node2 opt]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a9b48c6d7be2 swarm "/swarm join --addr=1" 3 minutes ago Up 3 minutes 2375/tcp node-2 

other information:

Swarm version: 1.2.6

Docker version: 1.12.6

Why is there such a problem? "Can not connect to the Docker daemon at tcp: //192.168.5.x: 2375. Is the docker daemon running?

One Solution collect form web for “When Docker Swarm discovery is file, how should the cluster be created?”

Heads up! This alert needs your attention, but it's not super important.