Docker Containers Exit Code 132
Docker Worked Properly as Usual with Existing Containers on My Computer (Like Kafka, Mysql, Postgres). Than I Wanted to Download New Version of Postgres and...
docker worked properly as usual with existing containers on my computer (like kafka, mysql, postgres). Than I wanted to download new version of postgres and docker run command always shows exit code 132.
Doesn't matter which container I want to start all of it is an immediate exit with 132
I checked docker events, docker logs but everything is empty.
Simple containers like hello-world can be started properly.
I found an article which mention sse4_2, but it's supported by CPU. As far as I remember there was no system update since it worked.
What can be the reason?
1 Answer
Step 1:
Check if your CPU supports amd64-avx:
$ sudo cat /proc/cpuinfo | grep avx
if it supports avx, it should high light avx but if not, it will return empty.
Step 2:
To solve the problem, run an image built to support amd64 and not amd64-avx this may mean you have to run an earlier version.
A good example of this is the mongodb docker images, the latest version supports amd64-avx and will refuse to run on CPUs that don't support avx and exist with error code 132.
But when you run version 4.4 of mongodb,it runs without any issue.
For more information on this:
Docker and -march native
Maya is a hardware enthusiast who tests and reviews smart home devices, smartphones, wearables, and audio gear. She focuses on practical consumer value and build quality.
