Open sumitkgaur opened 9 years ago
This output is related to the provisioning. We want to add "true" relation info by inspecting the cluster but we don't have it yet.
Yes, As a machine user I feel should be corrected to avoid false impression.
I am confused about what this issue means, there isn't a docker-machine info
command.
The title just has the command wrong, they meant docker info
:
Like so:
# docker-machine kill swarm-node-00
Forcibly halting swarm-node-00...
# docker info
Containers: 3
Images: 2
Role: primary
Strategy: spread
Filters: affinity, health, constraint, port, dependency
Nodes: 2
swarm-master: 192.168.180.222:2376
└ Containers: 2
└ Reserved CPUs: 0 / 1
└ Reserved Memory: 0 B / 1.021 GiB
└ Labels: executiondriver=native-0.2, kernelversion=4.0.9-boot2docker, operatingsystem=Boot2Docker 1.8.2 (TCL 6.4); master : aba6192 - Thu Sep 10 20:58:17 UTC 2015, provider=vmwarefusion, storagedriver=aufs
swarm-node-00: 192.168.99.100:2376
└ Containers: 1
└ Reserved CPUs: 0 / 1
└ Reserved Memory: 0 B / 1.022 GiB
└ Labels: executiondriver=native-0.2, kernelversion=4.0.9-boot2docker, operatingsystem=Boot2Docker 1.8.2 (TCL 6.4); master : aba6192 - Thu Sep 10 20:58:17 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 2
Total Memory: 2.043 GiB
Name: 548602cdcb56
Hi This looks like a bug in "docker info" command for swarm. I have created and then remove a slave node from the existing swarm cluster. "docker-machine ls" command display the outpout as expected but "docker $(docker-machine config --swarm master) info" command still show removed node in the cluster.
Thanks sumit