Adding nodes to docker swarm

We have a swarm running docker 1.13 to which I need to add 3 more nodes running docker 17.04.

  1. Is this possible or will it cause problems?
  2. Will it be possible to update the old nodes without bringing the entire swarm down?


  • Make Jenkins run docker without sudo
  • Identifying files contained within a docker image (or Application dependencies)
  • Node size on GKE kubernetes
  • WebSharper site working locally but not in docker
  • Docker as provider for Vagrant
  • Kubernetes - Persistent storage for PostgreSQL
  • Django show “It worked” page instead of my project when I start it docker
  • How to start another bash in Dockerfile
  • How to tell Docker client location of Notary Server?
  • Can't Ping a Pod after unbuntu cluster setup
  • Developing php with docker
  • Docker Compose shared CPUs
  • One Solution collect form web for “Adding nodes to docker swarm”

    I ran into this one myself yesterday and the advice from the Docker developers is that you can mix versions of docker on the swarm managers temporarily, but you cannot promote or demote nodes that don’t match the version on all the other swarm managers. They also recommended upgrading all managers before upgrading workers.

    According to that advice, you should upgrade the old nodes first, one at a time to avoid avoid bringing down the cluster. If containers are deployed to those managers, you’ll want to configure the node to drain with docker node update --availability drain $node_name first. After the upgrade, you can bring is back into service with docker node update --availability active $node_name.

    When trying to promote a newer node into an older swarm, what I saw was some very disruptive behavior that wasn’t obvious until looking at the debugging logs. The comments on this issue go into more details on Docker’s advice and problems I saw.

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