Baserow Docker Compose NumPy Error (Debian 12, Docker)

Technical Help
, ,
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

Baserow version 2.1.6

If you are self-hosting, which installation method do you use to run Baserow?

Docker version 28.5.2

What are the exact steps to reproduce this issue?

  1. Start container

I can’t start the Baserow all-in-one docker compose container. I am running a Debian 12.2.0 VM running Docker 28.5.2, other services occupying ports 80 and 443, and NumPy1 installed on the VM. When I start the container, I get this error message:
[CELERY_WORKER] RuntimeError: NumPy was built with baseline optimizations:
[CELERY_WORKER] (X86_V2) but your machine doesn’t support:
[EXPORT_WORKER] (X86_V2).
As far as I can tell, the issue is that Baserow 2.1.6 is trying to use NumPy2 but Debian 12.2.0 uses NumPy1. Is there any way to run NumPy1 through the docker-compose.yml? Or is there some other error that I’m missing?
Thanks

2

Managed to fix the problem! Downgrading to 1.35.3 only requires NumPy 1.x, and as a bonus you get to skip out on all of the AI additions :slightly_smiling_face:

New problem though — even with sufficient memory and CPU (assigned min 2G max 4GB and min 2 vCPU max 4 vCPU) the container shuts itself down after about 5 minutes

1 Like
3

Hey @Arcane

Problem with using NumPy v2 is related to CPU flags that NumPy requires.

Check what flags cpu on your host provide: grep -m1 'flags' /proc/cpuinfo

My guess would be that you have some generic cpu type defined on your host like qemu64 so try to change it into host or host-passthrough

Then check what flags your CPU has with above command and you should see X86_V2 there

As for using 1.35.3 - can you provide logs?