Exit Code 139Docker Exit Code 139
The container crashed with a segmentation fault (SIGSEGV, signal 11).
Exit Code 137The container was killed with SIGKILL (signal 9), commonly due to out-of-memory (OOM) conditions.
The process was forcibly killed (128+9=137). Most commonly caused by the container exceeding its memory limit (OOM killed). Can also be caused by docker kill, docker stop timeout, or Kubernetes eviction.
Check if OOM killed: docker inspect container_id | grep OOMKilled. Increase memory limit: docker run --memory=4g. Optimize application memory usage. Profile the application for memory leaks.
# Container killed (SIGKILL/OOM). Increase memory limit:
docker run --memory=2g myimageExit Code 139The container crashed with a segmentation fault (SIGSEGV, signal 11).
Error: toomanyrequests: Rate limit exceededDocker Hub's pull rate limit has been exceeded.
Error: No such containerThe specified container ID or name does not exist.
Exit Code 128The container process received an invalid exit signal.
OOMKilled: trueThe Linux kernel's OOM killer terminated the container because it exceeded its memory limit.
Error: port is already allocatedThe host port you are trying to bind is already in use by another process or container.