Docker container disaster recovery

I’m trying to run a service that does cron tasks using celery and it is very critical for our business. That certain container that runs the celery sometimes exits unexpectedly and I’m not being notified of the exit as well.

I have two questions:

  • How to recover from
  • Mount a windows host directory in compose file version 3
  • Adding files to bluemix volume
  • Docker Selenium-Chrome container memory utilization
  • docker-compose removing shared volume
  • How can write Dockerfile to start a webserver and curl it for some requirements
    • How can I be notified via e-mail if one of my container exits?
    • How to do a disaster recovery for example if that container exits or stops another container will start and continue the process of that exited container

  • How to let the docker container know itself is running with a host network?
  • binding of ports not working in docker
  • How do I wait for a pull?
  • How to connect to MongoDB running in Docker container?
  • Containerizing a web application using Docker: copy source code to multiple images?
  • CrashLoopBackOff in spark cluster in kubernetes: nohup: can't execute '--': No such file or directory
  • One Solution collect form web for “Docker container disaster recovery”

    you can start the docker container with the parameter:

    --restart="always"
    

    for example:

    docker run --restart="always" <IMAGE>
    

    for your first Q i would suggest to look into that link:

    How to programmatically monitor if a docker container exited?

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