Exit Code 137Docker Exit Code 137
The container was killed with SIGKILL (signal 9), commonly due to out-of-memory (OOM) conditions.
Exit Code 139The container crashed with a segmentation fault (SIGSEGV, signal 11).
The main process crashed due to a segmentation fault (128+11=139). This indicates a memory access violation, typically from a bug in native code, a corrupted binary, or an architecture mismatch.
Check if the binary is compiled for the correct architecture. Run with --platform flag if needed. Debug the segfault with core dumps. Ensure all shared libraries are compatible with the container's base image.
Exit Code 137The container was killed with SIGKILL (signal 9), commonly due to out-of-memory (OOM) conditions.
permission denied while trying to connect to Docker daemonThe current user does not have permission to access the Docker daemon socket.
Error: read-only file systemAn attempt to write to the container's filesystem failed because it is mounted as read-only.
OOMKilled: trueThe Linux kernel's OOM killer terminated the container because it exceeded its memory limit.
Exit Code 126The container's command was found but could not be executed.
Error: No such volumeThe specified Docker volume does not exist.