Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔍 Wheel glob and DCGM copy paths depend on the new image's layout
The image bump changes the contents of the source stage, and two later steps depend on that layout in ways the build cannot verify locally:
COPY --from=triton_source /usr/local/dcgm ...and/lib/x86_64-linux-gnu/libdcgm*.so*(lines 12-13) fail the build if those paths were dropped or renamed in the newer Triton image, anduv pip install /opt/tritonserver/python/triton*.whl(line 26) glob-matches whatever wheels the new image ships (historically bothtritonserver-*.whlandtritonfrontend-*.whllive there). Since the PR description states the build was not executed and no CI job builds this image, these are the concrete points to verify in a manual build before merging.Was this helpful? React with 👍 or 👎 to provide feedback.