Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/backends/tritonserver/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
# SPDX-License-Identifier: Apache-2.0

ARG DYNAMO_BASE_IMAGE="dynamo-base:latest"
ARG TRITON_SERVER_IMAGE="nvcr.io/nvidia/tritonserver:25.01-py3"
ARG TRITON_SERVER_IMAGE="nvcr.io/nvidia/tritonserver:25.11-py3"

Copy link
Copy Markdown
Contributor

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, and uv pip install /opt/tritonserver/python/triton*.whl (line 26) glob-matches whatever wheels the new image ships (historically both tritonserver-*.whl and tritonfrontend-*.whl live 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.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.


FROM ${TRITON_SERVER_IMAGE} AS triton_source

Expand Down
Loading