MongoDB Issue ( on VMS Mongo:latest does not start on missing sse4_2 Sets ) #8

Closed
opened 2026-02-16 12:51:02 -05:00 by yindo · 1 comment
Owner

Originally created by @ma-karai on GitHub (Oct 12, 2021).

MongoDB error 132

Known issue with MongoDB5, you can use a 4.4 version to run in on Virtualized machines that dont offer sse4_2 sets.

Cheers

Originally created by @ma-karai on GitHub (Oct 12, 2021). MongoDB error 132 Known issue with MongoDB5, you can use a 4.4 version to run in on Virtualized machines that dont offer sse4_2 sets. Cheers
yindo closed this issue 2026-02-16 12:51:02 -05:00
Author
Owner

@insertish commented on GitHub (Apr 29, 2022):

I've added a note to the README, but we will continue to ship MongoDB v5.
https://github.com/revoltchat/self-hosted/commit/51df0f07a036f0e278e836ce7dba61c565939327

@insertish commented on GitHub (Apr 29, 2022): I've added a note to the README, but we will continue to ship MongoDB v5. https://github.com/revoltchat/self-hosted/commit/51df0f07a036f0e278e836ce7dba61c565939327
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#8