vmware / vic

vSphere Integrated Containers Engine is a container runtime for vSphere.
http://vmware.github.io/vic
Other
639 stars 173 forks source link

swarm application: no healthy nodes #6396

Open mhagen-vmware opened 6 years ago

mhagen-vmware commented 6 years ago

Created a docker swarm with 3 nodes within a VCH. Swarm list returns all three:

anon@anon-Latitude-E7450:~$ docker -H 192.168.254.135:2375 run --rm swarm list token://e051e15c170f3a270db95f50b394777d
172.16.0.20:2375
172.16.0.22:2375
172.16.0.21:2375

docker info show all three nodes, but all their stats are empty:

anon@anon-Latitude-E7450:~$ docker -H tcp://192.168.254.135:2380 info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: swarm/1.2.8
Role: primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint, whitelist
Nodes: 3
 (unknown): 172.16.0.20:2375
  └ ID: 
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels: 
  └ UpdatedAt: 2017-09-19T17:04:24Z
  └ ServerVersion: 
 (unknown): 172.16.0.22:2375
  └ ID: 
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels: 
  └ UpdatedAt: 2017-09-19T17:04:24Z
  └ ServerVersion: 
 (unknown): 172.16.0.21:2375
  └ ID: 
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels: 
  └ UpdatedAt: 2017-09-19T17:04:24Z
  └ ServerVersion: 
Plugins: 
 Volume: 
 Network: 
Swarm: 
 NodeID: 
 Is Manager: false
 Node Address: 
Kernel Version: 4.4.71-1.ph1-esx
Operating System: linux
Architecture: amd64
CPUs: 0
Total Memory: 0 B
Name: f8dcfc5f8459
Docker Root Dir: 
Debug Mode (client): false
Debug Mode (server): false
WARNING: No kernel memory limit support
Experimental: false
Live Restore Enabled: false

And when I try to run a container I get the error:

anon@anon-Latitude-E7450:~$ docker -H tcp://192.168.254.135:2380 run busybox ls
docker: Error response from daemon: No healthy node available in the cluster.
See 'docker run --help'.

container-logs.zip

mdubya66 commented 6 years ago

@corrieb might want to see this