fix(ci): add --platform to aiperf-bench E2E docker build#674
Conversation
The aiperf-bench image build in the E2E action intermittently fails with "/bin/sh: no such file or directory" because the bare docker build lacks an explicit --platform flag. Without it, BuildKit may resolve the wrong architecture manifest for the python multi-arch base image. The Go validator images are unaffected (COPY-only, no RUN steps) and the release workflows already use docker/build-push-action with explicit platform matrix values. Fixes NVIDIA#673
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe E2E action's Docker build command for Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Co-authored-by: Mark Chmarny <[email protected]>
Summary
Add
--platform linux/amd64to thedocker buildforaiperf-benchin the E2E composite action to prevent BuildKit from resolving the wrong architecture manifest for thepythonmulti-arch base image.Motivation / Context
The E2E action intermittently fails building
aiperf-benchwith:The Go validator images (deployment, performance, conformance) are unaffected because they are COPY-only into distroless — no
RUNsteps, so/bin/shis never invoked. The release workflows (on-push.yaml,on-tag.yaml) are also unaffected because they usedocker/build-push-actionwith explicitplatforms:matrix values.Fixes #673
Type of Change
Components Affected
.github/actions/e2e/action.ymlTesting
--platformflagRisk Assessment
Low — additive flag on an existing
docker buildcommand. No behavioral change on correctly-configured runners; prevents failures on misconfigured ones.Checklist