Home > other >  Across the machine hanging storage, docker 2375 port is not up, leading to swarm query info node inf
Across the machine hanging storage, docker 2375 port is not up, leading to swarm query info node inf

Time:09-23

Generous solve bothers me, great god, and three problems are more than a month,
1. The swarm through token id set up successfully, a three physical machine, swarm the manage at first, then the swarm three list also can check the IP information,
What the problem is that the tutorial docker - H IP: port info here found out information are all zero, whether container or nodes, why? Tutorial has found out the info on information, each physical machine port 2375 also showed that the
2. So the problem 2, 2375 for not up? According to the tutorial in Riga DOCKER_OPTS docker configuration file="-h 0.0.0.0:2375 - H Unix:///var/run/docker. The sock", however, I haven't understand docker - d the meaning of this command, whether is open 2375 listening? If so, then I docker - d error:
WARN [0000] Running modprobe bridge nf_nat failed with message: that the error: the exit status 1
This error has appeared on my upgrade the kernel centos6.5, netizens said to upgrade the kernel, or recompile nf_nat, I chose to use centos7 directly, the result is an error, please answer,

3. The last question, the data volume container, used to hang at the mysql storage, this is a single physical machine, I have more than one physical machine, through the virtual network, can put the two docker0 through I understand, but mount data volume, container - volumes - from how to fill out the container name,? Or, how to through the port container link with mount data volume container,
Moreover, whether this is the docker swarm work? Kua machine mount data volume container,?

These three questions interlocking, troubled me for a long time, pretty good, can't break, these people still hope the great god, come to the rescue,
If successful, will certainly WeChat Lucky Money thanks ~!!!!!!

CodePudding user response:




- d - daemon=false daemon mode Enable


Docker with the storage of the docker to a path of physical machine, folder path, (what's this storage, docker should be dismissed)


CodePudding user response:

Urgent, urgent, urgent, online, etc.,
What a great god to see, my swarm after installation, see the node information is not correct, what reason, collapsed

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: swarm/1.
Role: the primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, the constraint
Nodes: 2
(unknown) : 10.135.47.39:2375
A ID:
A Status: Pending
A Containers: 0
A Reserved CPUs: 0/0
A Reserved Memory: 0 B/0 B
A Labels:
A Error: always connect to the daemon. The Docker Is the Docker daemon running on this host?
A UpdatedAt: the 2016-08-08 T01:59:30 Z
A ServerVersion:
(unknown) : 10.135.47.15:2375
A ID:
A Status: Pending
A Containers: 0
A Reserved CPUs: 0/0
A Reserved Memory: 0 B/0 B
A Labels:
A Error: always connect to the daemon. The Docker Is the Docker daemon running on this host?
A UpdatedAt: the 2016-08-08 T01:59:30 Z
A ServerVersion:
Plugins:
Volume:
Network:
Swarm:
NodeID:
Is Manager: false
The Node Address:
Security Options:
The Kernel Version: 3.19.0-39 - generic
Linux Operating System:
Architecture: the amd64
CPUs: 0
The Total Memory: 0 B
Name: 1 c6363959cac
Docker Root Dir:
The Debug Mode (the client) : false
The Debug Mode (server) : false
WARNING: No kernel memory limit support

CodePudding user response:

The solution? Online etc.!

CodePudding user response:

Swarm is how to install? Can try directly pull swarm mirror, with docker after each node to join the run - rm swarm list token://9145133 ce43fec9ff0fb42ba96916e42 to check information of nodes, each node of the docker listener port must be set up, unified set to 2375
  • Related