-
Notifications
You must be signed in to change notification settings - Fork 27
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 #42
Comments
Also, note that the output of |
Hello, thanks for detailed report. It looks like only Mongo 4.x supports your CPU. I have considered using older mongodb (latest version is 4.1.4 before they changed the license), but the latest version was considerably faster and it offered official precompiled binaries for windows. The latest mongodb version without AVX is 4.4.6. There are unofficial workarounds to build mongodb without avx, but nothing official. If you are running the system under a hypervisor, check if really your processor doesn't support this extended instruction set. Because you would need to have CPU older than 8 years to not have AVX, which is unlikely. |
A lot of server CPUs for low-consumptions servers also don't have AVX, which is my case. Will the software work with an older Mongo version? |
You can try to change base docker image in Dockerfile, but I won't support this old mongodb version, sorry. Often you can ask your hosting provider to move your VPS to another server, where AVX is supported. Closing as wont-fix. |
Expected Behavior
I can access the program from the web interface and it works
Actual Behavior
This has the same behavior as the one described in #32 .
Accessing the web interface gives me a fully white page.
Mongo complains about the CPU not having AVX support (see logs)
Steps to reproduce the problem
I am using the following
compose.yml
docker pull slada/dcef:main
sudo docker compose up -d --force-recreate
Specifications
Environment
DiscordChatExporter-frontend
DiscordChatExporter
--version
): v2.42.0How did you export the data?
--format
): Json--media
): Yes--markdown
): No--dateformat dd/MM/yyyy HH:mm:ss
,--reuse-media
Logs
Is there any relevant information in logs? If so, please provide them:
The text was updated successfully, but these errors were encountered: