docs: record onnx runtime docker fix

This commit is contained in:
2026-08-18 17:56:44 +08:00
parent 22dd55625f
commit a76c8d2613

View File

@@ -0,0 +1,58 @@
# Task: Stabilize ONNX Runtime Docker install
## Identity
- Task ID: 20260818-onnx-cuda-postinstall-a7c4
- Mode: Feature
- Branch: main
- Worktree: D:\Datas\OthersProjects\openmaic
- Base commit: 22dd55625fa5f855c6aa733ab6dd52bf2b878c96
- Owner: developer
- Status: Ready for integration
## Scope
- Record and verify the CPU ACK Docker fix for the `onnxruntime-node`
postinstall failure reported by Jenkins.
- Keep CUDA provider download opt-in; do not claim a GPU image is supported
without a CUDA-capable runner and a verified NuGet/proxy path.
## Intent And Constraints
- Linux/x64 `onnxruntime-node@1.23.2` assumes CUDA 12 when no install mode is
provided and rejects the Jenkins proxy's HTTP 302 response from NuGet.
- The CPU runtime and binding are bundled in the npm package, so the ACK image
should skip the unnecessary CUDA provider download.
- Preserve `pnpm install --frozen-lockfile`; avoid unrelated application changes.
## Outcome
- `OpenMAIC/Dockerfile` in base commit `22dd556` sets
`ONNXRUNTIME_NODE_INSTALL=skip` before the dependency-stage install.
- CUDA installation remains an explicit `cuda12` build-arg override and is
documented as requiring a CUDA-capable runner; it is outside this acceptance
scope.
- The lockfile correction is in `e1a0a14`, and the adopted `.project-docs/` tree
is tracked in `469f72b`.
## Verification
- The upstream install script exited 0 with `ONNXRUNTIME_NODE_INSTALL=skip`.
- Bundled Linux and Windows CPU runtime binding files were present.
- `git diff --check` passed.
- `check_project_docs.py` passed.
- Local Linux Docker validation is unavailable because the Docker Desktop Linux
engine pipe is not running; Jenkins must perform the end-to-end build.
- Final read-only reviewer returned `PASS`.
## Follow-ups
- Push `e1a0a14`, `469f72b`, and `22dd556` from an authenticated terminal, then
rerun the Jenkins CPU image build.
- If GPU deployment is required, provide a CUDA-capable runner image and verify
the `ONNXRUNTIME_NODE_INSTALL=cuda12` path against the organization's NuGet
proxy before enabling it.
## Promotion Candidates
- None recorded.