Swarm node Status down, but node should be Ready

I am trying to run a service on a swarm composed of three Raspberry PIs.
I have one manager and two worker nodes.

The problem is that sometimes the status of the worker nodes is “Down” even if the nodes are correctly switched on and connected to the network.

  • After building a docker image how can I run the image without pushing to docker hub?
  • can't connect to local mysql server through socket while running db using volume
  • Selenium for docker issue
  • Docker time measures in unified unit
  • Why is nginx returning a 502 when doing a `uwsgi_pass` to a linked docker container?
  • How to bring apache2 default web page im my browser with Dockerfile using jenkins
  • I just started using Docker so I might be doing something wrong, but everything seems to be correctly set.
    How would you avoid that “Down” status?

  • Dockerfile CMD not accepting variables
  • Docker Error: container id followed by “command not found”
  • How to tell Docker to use dm/LVM backend for volumes instead of vfs
  • Can a variable be used in docker FROM?
  • how to use docker and salt provisioning [closed]
  • Docker doesn't save data in host mounted volume
  • One Solution collect form web for “Swarm node Status down, but node should be Ready”

    It can depend on your exact version of docker, but your issue was seen in this thread

    A possible workaround was to do a docker ps, which seems to helped nodes to join the swarm.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.