Fix Blazor Wasm and Ntex Fortunes docker builds in CI

[LoopedBard3]

Both Blazor Wasm and Ntex Fortunes have been failing in benchmarks-ci-02 since mid‑April. The last green run was 20260326.1 on Mar 26; every run since has failed on a docker build --pull for one of these two scenarios. Both failures come from upstream dockerfiles outside this repo that have rolled forward in incompatible ways. Add local overrides under docker/ so the benchmarks repo controls these two builds directly.

Investigation

Reproduced both failing crank commands from build 2974764 on Docker Desktop:

• Blazor Wasm → docker build --pull --build-arg gitBranch=main -t benchmarks_dockerfile -f src/Components/benchmarkapps/Wasm.Performance/dockerfile .../src/Components/benchmarkapps/Wasm.Performance (log)
• Ntex Fortunes → docker build --pull -t benchmarks_ntex-db -f frameworks/Rust/ntex/ntex-db.dockerfile .../frameworks/Rust/ntex/ (log)

Blazor Wasm

dotnet/aspnetcore's wasm dockerfile installs Node.js 21 via https://deb.nodesource.com/setup_21.x. Node 21 went EOL in June 2024 and recent aspnetcore npm dependencies require node 18 || 20 || >=22:

npm WARN EBADENGINE Unsupported engine { package: 'balanced-match@4.0.4', required: { node: '18 || 20 || >=22' }, current: { node: 'v21.7.3', npm: '10.5.0' } }
npm WARN EBADENGINE Unsupported engine { package: 'brace-expansion@5.0.5', ... }
...
[!] Error: require() of ES Module /src/node_modules/@tootallnate/once/dist/index.js from /src/node_modules/http-proxy-agent/dist/agent.js not supported.
Error [ERR_REQUIRE_ESM]: ...
npm ERR! Lifecycle script `build:debug` failed with error

Ntex Fortunes (and Ntex Plaintext / Ntex Json)

TechEmpower's frameworks/Rust/ntex/Cargo.toml uses ntex-bytes = { version = "1.5", features=["simd"] } — caret semver, so cargo resolves to the newest 1.x. ntex-bytes 1.6.0 shipped 2026-05-02 and introduced the BytePages type, which the fafhrd91/postgres ntex-3 tokio-postgres fork (frozen at fbc7a17) does not understand — it still uses BytesMut. Because the workspace builds tokio-postgres for every binary when --features=tokio is set, all ntex docker builds fail with E0308 mismatched-types errors, not just the database scenario:

error[E0308]: mismatched types
   --> /usr/local/cargo/git/checkouts/postgres-.../tokio-postgres/src/query.rs:77:52
   |
77 |             encode_bind(statement, params, "", buf)?;
   |             -----------                        ^^^ expected `&mut BytesMut`, found `&mut BytePages`
error: could not compile `tokio-postgres` (lib) due to 9 previous errors

Fix

Two narrowly-scoped overrides:

1. docker/wasm-performance/ — copy of upstream's dockerfile, exec.sh, and a new benchmarks.compose.json, with setup_21.x → setup_22.x and the source repo pointing at this repo so crank picks up the override. build/job-variables.yml now points blazorWasmJobs at the local compose JSON.

2. docker/ntex-techempower/{ntex-plt,ntex-db}.dockerfile — a thin replacement that clones TechEmpower master from inside the container, then sed -i pins ntex-bytes to =1.5.4 before cargo build. scenarios/te.benchmarks.yml updates the ntex job and the fortunes_ntex override to source these from aspnet/Benchmarks instead of the TechEmpower checkout.

Verification

Ran the exact crank docker build --pull invocations locally on Docker Desktop after both fixes:

Image	Result
benchmarks_wasm_node22 (upstream dockerfile + setup_22.x)	✅ build + publish succeed; produces playwright runtime image
test_wasm_local (local override under docker/wasm-performance/)	✅
test_ntex-plt_local (local override)	✅ Finished release profile [optimized] target(s) in 52.40s
test_ntex-db_local (local override)	✅ same, both ntex-db and ntex-plt binaries produced; Cargo.lock shows ntex-bytes 1.5.4 as expected

Notes for follow-up

Both overrides are intentionally temporary:

• Drop docker/wasm-performance/ once dotnet/aspnetcore bumps to Node 22 upstream.
• Drop docker/ntex-techempower/ once fafhrd91/postgres ntex-3 is updated for ntex-bytes 1.6+ (or TechEmpower itself pins ntex-bytes).

[LoopedBard3]

Closing in favor of some more direct approaches for fixes.