Is there a way to make docker containers truly fault-tolerant?

I mean fault tolerance as in running a backup container and constantly synchronizing the active containers state (memory) to the passive one, so in case of failure i can failover to the other container without losing active network connections or state of the application running inside the container?

I know docker swarm exist, that can make my containers highly available by restarting them on other nodes in case of node failure, or even making the service fault-tolerant by replication, but this will only work if my service is either stateless or saves it’s state in a shared network storage or database.

  • Docker - Unable to use placeholders inside ENTRYPOINT
  • Azure App Service + Docker Autodeploy?
  • Issue with docker compose: container command not found
  • Running Docker Image
  • Error while cleaning images from docker
  • How to forward all ports in docker container
  • I’m looking for a solution like vSphere FT just for docker.

  • ERROR: Service 'redis' failed to build. When building redis image by docker-compose
  • How to filter docker process based on image
  • how to set supervisor to run a shell script
  • Docker copy on write with big files
  • how to set max_execution_time php-fpm docker image?
  • Deploy/run a Redis service using Ansible and Docker
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.