Repository navigation
fix(vm): bind cached registry images to verified manifest digests - #4342
Conversation
Signed-off-by: Adrien Langou <alangou@nvidia.com>
|
Label |
|
🌿 Preview your docs: https://nvidia-preview-pr-4342.docs.buildwithfern.com/openshell |
Maintainer Approval NeededGator completed its independent code review of the VM registry cache fix and found no blocking findings. Required checks are green on the current head, including core E2E and both managed and external VM E2E paths. Action required: a maintainer should review and approve this PR. Gator metadata
|
Monitoring CompleteMonitoring is complete because this PR has merged. Final status: Gator review found no blocking findings, and the last recorded required checks and E2E results passed. I removed the active Gator metadata
|
Summary
Bind VM registry downloads to the manifest digest used for the image cache identity. Resolving a tag and then pulling it independently could cache different image contents under the resolved digest; both VM registry preparation paths now pull through an immutable digest reference and reject mismatched manifest bytes before downloading blobs.
Related Issue
None.
Changes
Testing
/dev/kvm. Thetest:e2elabel requests the repository's core E2E lane.The parallel VM unit suite hits
driver::preparation::tests::restart_reclaims_inactive_attempts_and_preserves_active_shared_and_unknown_data; the same failure was reproduced on the unmodified baseline. The complete serial suite passes. Registry tests validate manifest verification and staging without booting a VM; successful-manifest cases deliberately stop at a missing blob response.Checklist