Docker container exited with code 132

Good morning,
have the same problem (see Mongo:latest does not start on missing sse4_2) with mongodb:latest (which is version 5). Running the older (and still maintained) version 4 the container is starting fine.
I guess that the v5-image refuses to start due to missing features on the CPU as mongodb ends with “illegal instruction”.
There is already an issue for this on github:

Quick way to solve it is to use the image mongodb:4 instead of mongodb:latest

2 Likes