Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Will Not Implement
Created by Chair Shíín
Created on Nov 17, 2025

AVX compatibility

What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

mongodb4.4 no image nowhere


Hello MongoDB Team,

Congratulations — you managed to waste 6 hours of my time today.

There is no usable MongoDB 4.4 image anywhere (Docker Hub / Quay / official images / community images). Absolutely nothing that works on Fedora Server under Podman, and nothing that works on non-AVX CPUs.

And why?
Because you decided to drop AVX-less CPU support without providing any fallback images, any warnings on the repos, or any maintained legacy builds.
So now I’m stuck in a situation where your arbitrary decision forces me to switch operating systems just to run an older MongoDB version — which will be another 6 hours of pointless bullshit.

If you remove CPU support, at least provide:

  • a working container image

  • a clear compatibility table

  • or something that doesn’t make users dig through 20 dead repos and error logs.

Right now it feels like you simply said: „Screw everyone with older hardware.”
Well, thanks. Really great developer experience.

Please fix your container availability and compatibility docs, or publish proper legacy builds.

— Extremely frustrated user

What would you like to see happen?

Describe the desired outcome or enhancement.

give us back the fcking image min. backports, tarball something

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

BASSZÁTOK MEG! 1-SZER

BASSZÁTOK MEG! 2-SZER

BASSZÁTOK MEG! 3-SZOR

What steps, if any, are you taking today to manage this problem?

BASSZÁTOK MEG!


  • Admin
    Dan Mckean
    Dec 2, 2025

    Hi, we appreciate and apologize for the frustration.

    Unfortunately if that was a conscious decision we made at some point, it's several years old at this point and this hasn't come up from customers in that time. So right now we've no plans to support AVX-less CPUs.

    Similarly, in our docs we have to document what we do support, rather than what we don't. Otherwise we risk missing something (like this) that we don't support but we're not even conscious of.