Why docker stops already running containers during startup?

I have some containers running with docker server up. Now if the daemon crashes for some reason (I killed it using kill -9 $Pid_of_daemon to reproduce this behavior), and if I start the docker server again, why does it kill the old running container. The behavior I want is it should go ahead even if there are already running containers. The only reason I found out is, when daemon crashes, it looses its stdin, stdout pipes with the container, so it can no more attach to the old running containers. But if my container does not want stdout, stdin or stderr, then why would the daemon is killing it during startup. Please help

  • docker nginx deployment entrypoint
  • Cant get docker run -v to work
  • How do you include binaries from an OS image service with docker compose?
  • Unable to connect to dockerized postgres on localhost, but remote connection is working
  • “Not a tty” error in Alpine-based duplicity image
  • Running rust on Docker: Empty reply from server
  • Docker java.lang.RuntimeException when attempting to build error
  • How can I install docker toolbox on windows 7
  • Docker and systemd - service stopping after 10 seconds
  • Docker - How to Inspect Container for Volume Path?
  • Syntaxnet spec file and Docker?
  • AWS ECS - Images from S3
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.