-
Notifications
You must be signed in to change notification settings - Fork 633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB 5.0+ requires a CPU with AVX support. Container failed to start #619
Comments
The warning is there to let you know why the container is mysteriously crashing (since there is no output from the crashing MongoDB binaries). I'm a little confused 😕. Are you saying that on one machine that you upgraded docker from If these are separate machines, then it is expected that one might not run it even though it is on a newer version of Docker. The version of Docker is not relevant to this error. The |
I am trying to run on totally new server.
Also tried downgrading the docker to the old version i.e. Since we are running on the container can we solve this by adding some configuration to it? |
If the CPU doesn't have that avx capability, you can pin mongo to an older version like |
Nope, the compiled MongoDB binaries (5.0+) require a CPU with specific instruction support. There is nothing we can do from the Docker side. |
FWIW I worked around this by replacing the binaries in the MongoDB docker image with self-compiled versions with a different '-march' flag. More details and links to a docker image to help with mongodb compilation on the linked issue here: #485 (comment) |
Docker container is not starting and It only shows warning on docker logs
Docker version : 23.0.4, build f480fb1
Docker-compose version: v2.17.2
docker-compose.yml
Output:
This same code is running well on
docker: 20.10.23, build 7155243
docker-compose: 1.29.2, build 5becea4c
The text was updated successfully, but these errors were encountered: