We occasionally get failing builds due to docker container for elasticsearch failing with a message
Exited with code 137. This message appears at the end of normal output you see after successfully spinning up the docker container, without any additional information.
Apparently this is due to the container running out of memory. Considering this message happens right away, it’s not likely to be due to load (nothing is happening yet), but rather an underlying misconfiguration, and/or resource-hungry neighbors.
This issue is blocking production deploys for us. Any chance this could get resolved quickly?