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.

  • How to setup Docker for a polyglot microservice-based application?
  • 502 error when viewing Java liberty Bluemix application using Docker container
  • Docker how to map subdirectory to port
  • Docker: Strider CD dashboard assets broken on installation
  • PHPStorm, Docker and debugging
  • Cannot login to docker container registry which is inside docker container
  • 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?

  • How do I select the master Redis pod in this Kubernetes example?
  • Docker LAMP stack - lstat apache_default: no such file or directory?
  • Dockerfile - Angular2
  • Create a remote private registry
  • Docker can't connect containers
  • Restricting file access of Docker container
  • 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.