Sometimes you have to investigate a container, which is stopped, or a container which after starting up dies very quickly and stops.
docker exec -ti <id> bash only works on running containers, once it finishes, the bash prompt terminates as well.
docker start you cannot supply a different command, and if the container dies abruptly again you won't have enough time to get into the container and do your investigations.
We can do
docker commit, then
docker run on the new image with a different command, but I'm wondering if there are any other alternatives.
docker logs just returns whatever the apps printed to stdout/stderr. That might not be enough to figure out what the problem was.