DockerContainer doesn't start/restart exited or stopped containers

If a container that corresponds to a DockerContainer component for an active deployment is in the stopped or exited state, running adapt update should either start or replace the container to bring it back to a running state, but currently DockerContainer does not. DockerContainer recognizes that the container already exists, but does not check for it to be in the running state.