Docker exec command is failing with EXIT CODE 137

Question

I am running a CICD pipeline that runs a test script inside a docker container with docker exec and its failing with a return code of 137 every 3rd or 4th time. Here is the code that's running:

docker-compose -p 1234 -f docker-compose.yml exec -T webapp run_tests.sh
STATUS=$?
...
docker-compose -p 1234 -f docker-compose.yml logs --no-color webapp
...
exit $STATUS

Thing is whenever it fails with EXIT CODE 137, container gets killed immediately and there are no logs available for debugging. I think 137 is caused by some external process but I am not able to trace it. Any insights into this will be very helpful.

vanelo · Accepted Answer · 2022-05-17 16:32:33Z

2

Thanks for your question, I experience a related error and it was related to a memory limit, try to increase your swap memory. Here a link with someone with similar problem

answered May 17, 2022 at 16:32

vanelo

214 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Erlang Parasu · Accepted Answer · 2022-12-06 06:11:32Z

1

I experience related error too, in my case i got error when executing docker-compose exec on my Jenkins build. Fixed by add deploy config to docker-compose.yaml to increase memory limit

# docker-compose.yaml
version: '3.8'
services:
  app:
    image: my-app:1.0.0
    build:
      context: .
      dockerfile: ./Dockerfile 
    # ports: 
    # networks: 
    # volumes: 
    # depends_on: 
    deploy:
      resources:
        limits:
          memory: 500M
        reservations:
          memory: 128M

Try changing deploy.resources.limits.memory and deploy.resources.reservations.memory

Ref: https://docs.docker.com/compose/compose-file/deploy/#resources

answered Dec 6, 2022 at 6:11

Erlang Parasu

4032 gold badges6 silver badges11 bronze badges

Collectives™ on Stack Overflow

Docker exec command is failing with EXIT CODE 137

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related