Error guides tagged [docker]

Docker cannot communicate with the Docker daemon because the daemon is stopped, inaccessible, or the current user lacks permission.

The container was terminated abruptly by the host operating system because it ran out of memory (OOM) or received a SIGKILL signal.

The Docker command-line client cannot establish a connection because the background Docker daemon process is not running on the system.

The Docker builder engine failed to parse the Dockerfile due to syntax typos, incorrect instruction keywords, or malformed formatting.

The current user does not have read/write access to the Unix socket file (/var/run/docker.sock) used to communicate with the Docker daemon.

The Docker CLI command itself failed to run, often due to syntactically invalid parameters or driver failures before the container process could start.

The command specified inside the container was found, but it could not be executed due to permission limitations or file format issues.

The command specified inside the container could not be found, or its interpreter (shell) is missing in the base image.

The containerized process was forcefully terminated by a SIGKILL (signal 9) signal from the host, typically due to memory exhaustion.

The BuildKit compiler engine failed to compute the build steps (LLB definition) due to missing files, incorrect paths, or registry authorization errors.