You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, living in a system admin world all my adult / professional life I get the need to keep systems up to date and software up to date. However I have to ask: Is there a solution to MongoDB 5 requiring the AVX instruction set? I realize that AVX was shipped with Haswell back in 2013 and thus 11 years is more than enough in the technical world to assume most people are running on it, but Xeon processors are RAMPANT in many home labs given the costs of systems.
Would it be too much to ask to release a dockerfile version for a Pre 5.x MongoDB installation that would work on older server hardware? It's not as if 5eAPI requires a honking system to run, the restriction is simply in the chosen software version at build time.
The text was updated successfully, but these errors were encountered:
As far as I'm aware, this is due to the nature of where the docker instance is built. I run an M2 laptop and get the same error. I have to rebuild locally to avoid this error when I'm testing locally. Rebuilding locally should also fix this for you. I'm not sure the correct way to build this with Github actions so it doesn't have this error.
So, living in a system admin world all my adult / professional life I get the need to keep systems up to date and software up to date. However I have to ask: Is there a solution to MongoDB 5 requiring the AVX instruction set? I realize that AVX was shipped with Haswell back in 2013 and thus 11 years is more than enough in the technical world to assume most people are running on it, but Xeon processors are RAMPANT in many home labs given the costs of systems.
Would it be too much to ask to release a dockerfile version for a Pre 5.x MongoDB installation that would work on older server hardware? It's not as if 5eAPI requires a honking system to run, the restriction is simply in the chosen software version at build time.
The text was updated successfully, but these errors were encountered: