Test in Docker container fails with error 137 indicating a probable memory leak #25492
-
This command is supposed to run jest
and this is supposed to run cypress
My repository works fine in local computer but fails in github actions. Link to my repository: https://github.com/pvgdev/nextjs-template |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Error 137 in Docker denotes that the container was killed by ‘OOM killer’ (Out of Memory). This happens when there isn’t enough memory in the container for running the process.
To resolve error 137 in Docker, you can try with the following steps:
To view more details about container’s resource constraints, you can see “Runtime options with Memory, CPUs, and GPUs”. |
Beta Was this translation helpful? Give feedback.
@pvgdev,
Error 137 in Docker denotes that the container was killed by ‘OOM killer’ (Out of Memory). This happens when there isn’t enough memory in the container for running the process.
The 2 main out-of-memory reasons:
Docker container has run out of memory
By default, Docker containers use the available memory in the host machine. To prevent a single container from abusing the host resources, there may be some memory limits set for per container on the virtual machines of GitHub-hosted runners.
It is important not to allow a running container to consume too much of the host machine’s memory.
Docker host has no free memory
Each virtual machine of GitHub-hosted runner has the same har…