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.

  • Why does creating a file inside a docker-machine VM result in permission denied?
  • Docker and Eureka with Spring Boot failing to register clients
  • How can I maximize throughput in Docker and Akka HTTP?
  • WSO2 Carbon/API/DSS/ESB - Docker Restart
  • Docker image for windows components
  • docker mysql-server not starting on ubuntu [closed]
  • I’m looking for a solution like vSphere FT just for docker.

  • Running windows containers and linux with the same docker client [closed]
  • Setting volumes in docker-compose.yml file for windows 10 home
  • Docker: Remove and create folder before doing cp
  • How to do local development with Kubernetes?
  • How to query Docker DNS from within a container?
  • Docker apt-get update fails
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.