Skip to content

Build numpy without a fixed SIMD baseline in the Docker image #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Robbie1977 merged 1 commit into from
Aug 26, 2026
Merged

Build numpy without a fixed SIMD baseline in the Docker image #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,17 @@ RUN apt-get update && \
apt-get install -y --no-install-recommends gcc g++ && \
rm -rf /var/lib/apt/lists/*

# Build numpy from source with no fixed SIMD baseline. The PyPI wheels for
# numpy >= 2.4 are compiled for x86-64-v2 (SSE4.2/POPCNT) and refuse to import
# on the VFB Rancher/k8s hosts, whose QEMU "qemu64" CPU model does not expose
# those flags. cpu-baseline=none keeps every SIMD path as a runtime-dispatched
# option (X86_V2/V3/V4 are still used where the CPU has them), so there is no
# speed cost on modern hosts. Installed first so pip treats the numpy
# requirement from vfb_connect/pandas as already satisfied.
ARG NUMPY_SPEC=numpy
RUN pip install --no-cache-dir --no-binary numpy \
-Csetup-args=-Dcpu-baseline=none "${NUMPY_SPEC}"

# Install Python deps first (layer caching)
COPY requirements.txt setup.py pyproject.toml README.md ./
COPY src/ src/
Expand Down
Loading