[Bug]: MongoDB Container Requires AVX Support on Non-AVX Systems

[shahabafshar]

What happened?

The MongoDB container fails to start on systems that do not support AVX (Advanced Vector Extensions) because MongoDB 5.0+ requires AVX support. This issue is particularly problematic for users running MongoDB in Docker containers on older hardware or virtualized environments that do not expose AVX features to the VM.

I expected the MongoDB container to start without requiring AVX support, or at least to have a clear alternative version of MongoDB that is compatible with non-AVX systems.

The lack of support for non-AVX systems in MongoDB 5.0+ versions causes significant inconvenience for users with older hardware. It would be beneficial to provide a MongoDB image that is compatible with these systems or to document a workaround for affected users.

Suggestion:
It would be beneficial for users with non-AVX compatible systems to have clear documentation or a version tag available for MongoDB images that do not require AVX support. Specifically, using MongoDB version 4.4.18, which is the latest version without the AVX requirement, could be highlighted as an alternative for those affected by this hardware compatibility issue.

Here is an example of how the Docker configuration can be adjusted to use MongoDB 4.4.18: (TESTED AND WORKS FINE)

mongodb:
    container_name: chat-mongodb
    image: mongo:4.4.18
    restart: always
    user: "${UID}:${GID}"
    volumes:
      - ./data-node:/data/db
    command: mongod --noauth

### Steps to Reproduce

1. Attempt to start a MongoDB 5.0+ container on a system without AVX support.
2. Observe the warning message indicating the lack of AVX support.
3. The MongoDB service fails to start.

### What browsers are you seeing the problem on?

_No response_

### Relevant log output

```shell
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
see https://jira.mongodb.org/browse/SERVER-54407
see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Feel free to make a PR to update the documentation, as this is a solid use case for using a docker-compose.override.yml file: https://docs.librechat.ai/install/configuration/docker_override.html

The compose files provided are not meant to cover every possible case. In fact, for more advanced users, it's encouraged they write their own up to their specifications. An easy way to "modify" the existing file, as this is enough for most users, is to make use of an override file.

[shahabafshar]

I appreciate the flexibility offered by the docker-compose.override.yml file. However, I’d like to suggest setting the default MongoDB version in the primary docker-compose.yml to 4.4.18 for enhanced out-of-the-box compatibility. This could help avoid common issues with AVX support, making initial setup smoother for most users. Advanced users could still use the override file for more specific configurations.

Thank you for considering this improvement to accommodate a wider user base.

[AumCoin]

Using the docker override file in the project resolved this simply, but I agree that if upgrading mongo causes issues and solves none then perhaps mongo should be kept on the older version, since it took me a little while to figure out what was going on and find this thread.

[gsaiz]

For any fellow Proxmox users, this is also an issue if you run LibreChat on a VM that has the CPU type set to a value that doesn't have the AVX flag.

In my case, it was because I use terraform to deploy the VM in Proxmox, which for some reason sets the default cpu type to qemu64.

Changing the CPU type to host, as suggested in this support thread in Proxmox forums, solved it.