I ran a subprocess in Python. I don’t think the subprocess itself is exiting abnormally and in either case, I catch the exception in the code if it does. What happens is that the Docker container itself dies with a 137 exit code. I didn’t see an OOM error when running Docker inspect. Also, when monitoring the memory utilization, it doesn’t come close to the limit. I’m running Docker version 18.06.1-ce, build e68fc7a and docker-compose version 1.22.0, build f46880fe.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Docker process dies with exit code 137, but no OOM error | 0 | 3241 | October 14, 2018 | |
| Docker Process Exited with Code 137, but not due to OEM | 0 | 1751 | October 15, 2018 | |
| Docker containers getting killed with exit code 137 and OOMKILLED false | 1 | 1477 | November 1, 2023 | |
| Container fails with error 137, but no OOM flag set (and there's plenty of RAM) | 11 | 22796 | August 10, 2021 | |
| Docker container still returns exit code 247 with Python Flask API after increasing Memory resource and memory-efficient code implementation | 0 | 718 | December 19, 2023 |