What's the reason that stopped containers are kept around? Can they be restarted in any way?

Because you want to keep uncommitted changes around for recovery, image creation, or general inspection. Stopped containers can be restarted with the command <code>docker start <container-name></code> and can be viewed with a <code>docker ps -a</code> In addition you can commit changes for any container (even if the container is stopped) to your local registry with a <code>docker commit <container-name> <repository>:<tag></code>

Why does Docker keep around the stopped containers?

1 Answers

Because you want to keep uncommitted changes around for recovery, image creation, or general inspection.

Stopped containers can be restarted with the command docker start <container-name> and can be viewed with a docker ps -a

In addition you can commit changes for any container (even if the container is stopped) to your local registry with a docker commit <container-name> <repository>:<tag>