Add a dedicated 'Start' command for stopped containers

Author: milkosanchezCreated Aug 27, 2026Updated Aug 27, 2026
Labelsenhancement

Hi! I noticed that when a container is stopped externally or crashes, lazydocker often gets out of sync and still thinks the container is running. Because of this, pressing 's' triggers a "Do you really want to stop this container?" confirmation instead of starting it.

Since starting a container is a core action, it would be amazing to have a fallback or a dedicated keybind/menu option explicitly for starting exited containers, instead of relying solely on the dynamic state toggle which frequently experiences sync issues with the Docker daemon.

As a temporary workaround, I had to manually register a custom command in config.yml: command: "docker start {{.Container.Name}}"

It would be awesome to have this natively supported or better synchronized out of the box!

Source: jesseduffield/lazydocker