6.2.1.1 Detached Background Execution

Detached background execution describes how a container started with -d continues running entirely independently of the terminal session, process, or script that launched it, persisting even if that originating terminal is closed or the launching process itself exits.

The Container Outlives Its Launching Terminal

Because Docker's daemon, not the terminal, is what actually manages a running container, closing the terminal that issued docker run -d has no effect on the container's continued operation.

docker run -d --name myapp myapp:1.0
exit

Closing this terminal session entirely, the container continues running, managed by the daemon independently of any specific terminal.

Verifying Continued Operation After the Launching Session Ends

Reconnecting later, even from an entirely different terminal session, confirms the container is still running exactly as it was left.

docker ps --filter "name=myapp"

Why This Independence Is Essential for Production Use

A production service cannot depend on a specific terminal session remaining open indefinitely — detached background execution decouples the container's actual operational lifetime from any particular session, script, or connection that happened to be used to start it.

ssh server "docker run -d myapp:1.0"

Even though the SSH session that issued this command will eventually close, the container continues running on the remote server, entirely independent of that specific connection's lifetime.

The Daemon, Not the Client, Is What Actually Matters

Docker's command-line client is just an interface to the daemon, which is the actual process responsible for managing running containers — as long as the daemon itself remains running, containers it manages continue operating regardless of what happens to any client session.

systemctl status docker

Why Detached Background Execution Matters

Understanding that a detached container's continued operation depends on the daemon, not any particular terminal or client session, is foundational to correctly reasoning about container reliability and availability in any real deployment scenario.