UniFi app not detecting AVX CPU flag

Apps and Virtualization
1

I’ve been running a UniFi app inside a TrueNAS box with an Intel Core i7-2600 CPU.

However, the last version of the app (2.1.3) will not deploy on this machine, with the log stating that “*** THE x86_64 CPU in THIS SYSTEM DOES NOT SUPPORT AVX EXTENSIONS ***”

I have confirmed that this CPU has AVX extensions; not only that, but opening a shell into other running apps in the same box and running

grep avx /proc/cpuinfo

shows that the flag is being passed to the Docker containers.

Is there a way to force a container to recognize that the CPU does indeed have AVX extensions?

2

There’s a decent chance the App needs AVX2, not just AVX and the message simply hasn’t been updated.

MongoDB 5 lists Sandy Bridge (core 2000) as a minimum while MongoDB7 wants Haswell (core 4000), see Production Notes for Self-Managed Deployments - Database Manual v7.0 - MongoDB Docs

In general there’s relatively little software that just uses AVX, not AVX2 since there’s very few CPUs that have just AVX without immediately using AVX2.

The x86_64-v2 baseline doesn’t include any AVX (just SSE 4.2) and v3 immediately jumps to AVX2

3

Thank you; that’s probably the issue - my CPU does not have AVX2 extensions.

I was waiting for an excuse to change the customer’s router from an old EdgeRouter to a Cloud Gateway and native UniFi support - that’s the easiest (though not cheapest) way.

Have a great week!

4

FWIW, running UniFi OS Server on this same machine, inside a Debian VM, works, even though there is no support for AVX2…