docker swarm stop containers on quorum loss

This is a somewhat simplified scenario, but I would like to know how people deal with these kinds of problems.

I have a docker swarm consisting of 3 managers and a service that writes to a network volume. The service should therefore run only once, so there are no conflicts. I would like it to restart on a different host if it’s current host dies. The problem is that if the current host loses it’s connection to the other hosts. The service continues running on that host and is also restarted on one of the two remaining hosts because they still have the quorum. This results in 2 instances of the service which could lead to conflicts.

  • How to link binaries between docker containers
  • Setting up Text editor like Vim,Spacemacs to work with docker containers without installing tools on the host machine
  • How to run 2 wordpress blogs using docker on ec2
  • Mount host directories in docker compose
  • Docker compose with two files
  • What are the security and performance constraints of using docker containers in a RESTful API in order to execute untrusted code?
  • How to debug a rails app in docker with pry?
  • Using host machines CA cert within Docker container
  • Install docker on RedHatLinux 6.7
  • Data is lost in Mysql docker container after comminting it to a new image?
  • How can I get 2 containers to link when I get an EOF error
  • Running gunicorn inside heroku docker
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.