Builds broken since ~July 5: OOM (exit 137) + headless Chromium can't launch in builder (worked June 30)

Question

Hi,

Our Docker image builds started failing on July 5, 2026, with NO changes to build inputs (same requirements.txt and Dockerfile stages that built green on June 30). Two distinct failure modes, both pointing at builder infrastructure changes:

1) OOM kills during `pip install` (exit code 137)

process "/bin/sh -c pip install --no-cache-dir -r requirements.txt"

did not complete successfully: exit code: 137: context canceled

It died at a DIFFERENT package on each attempt (classic memory-pressure symptom, not a bad wheel). Our Dockerfile is multi-stage; BuildKit runs the Node frontend stage and the Python stage in parallel, and their combined memory peak now exceeds the builder's limit — it didn't on June 30.

2) Headless Chromium can no longer launch in the builder

After we serialized the stages (fixing the OOM), the build failed at our puppeteer prerender step — Chromium exits immediately on launch:

[frontend-build 7/7] RUN npm run build

ERROR:dbus/bus.cc:405 Failed to connect to the bus...

ERROR:third_party/crashpad/... open /sys/devices/system/cpu/cpu0/cpufreq/...

at ChildProcess.onClose (@puppeteer/browsers/lib/esm/launch.js:339:24)

process "/bin/sh -c npm run build" did not complete successfully: exit code: 1

This is with --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage already set, using Debian's system Chromium (node:20-slim stage). The exact same step ran fine in your builders on June 30.

We upgraded to Pro DURING this incident — it made no difference to either failure, which further suggests builder-level limits rather than plan resources.

Failed deployments: July 5, 2026, ~17:00–18:15 UTC, services api/worker/beat (GitHub zuevskiy11-dot/Content-factory, branch main; commits a92c721, bc2da9d, 6246b0e). We've worked around it by removing the prerender from the image build (commit e8c8c53, built green), but we'd like the prerender back.

Questions:

1. Did builder infrastructure change between June 30 and July 5 (memory limits, sandboxing/seccomp, kernel)?
2. What are the current build-time memory limits on the Pro plan?
3. Is running a headless browser (Chromium via puppeteer) inside an image build supported? If yes, what configuration is required now?

Thanks!