Docker container stops immediately after start up with exit code 132

Hi, I am running a docker compose yml file using docker-compose which is starting 4 different services: docker-compose -p name -f docker-compose_production.yml up --build

However, after building, the containers built from the services seem to immediately exit with code 132 in the console:

service1_container exited with code 132
service2_container exited with code 132

I then run “docker ps -a” to get the ids of the exited containers (with status Exited (132) x minutes ago) and then run “docker logs ” to access the logs, however it returns nothing:
Screen Shot 2023-06-09 at 10.12.25 AM

The parent container image I’m using in my dockerfile is qiime2 ( Older versions of the image don’t crash the deployment, but newer versions do. I suspect it might be something to do with newer versions breaking, but I would like to see some error logs to identify the root issue.

How would I find out the cause of why the containers are exiting? I’m not sure if the logs are empty because there’s actually nothing or if I’m supposed to access the logs in a different way.

I don’t know the image, but it is completely possible that there are no logs because it failes before it could write anything. In order to find out what it was caused by, you should find out what the error code means in case of the software that is running in the container. The maintainer of the image could probably tell you what the error code means. I also found the community forum of qiime2

They can probably help you more, but I can share some general ideas:

  • Sometimes the host operating system is not compatible with the container. It is rare, but it can happen.
  • It could be that the parameters, configurations have changed and your old parameters make the container fail created from the new image.
  • Sometimes the Docker version is too old and some system calls can’t doesn’t work through Docker.
  • Sometimes the logs are not properly sent to the standard output and error stream so you don’t see it with docker logs but you can browse the content of a stopped container or copy the content out to investigate.

I talked about some ideas on a Docker Community All-Hands event and there is also a blogpost about it where you can find my video too: