docs: use prebuilt gpt-oss container

[nealvaidya]

Summary by CodeRabbit

• Documentation
  • Updated setup instructions to use a prebuilt container image by default.
  • Introduced a new environment variable for specifying the container image.
  • Added a collapsible section with manual build instructions for advanced users, including commands for different architectures.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

Walkthrough

The documentation for GPT-OSS deployment was updated to recommend pulling a prebuilt container image instead of building one from scratch. A new environment variable for the image URL was introduced, along with a collapsible section that provides manual build instructions for different architectures.

Changes

Cohort / File(s)	Change Summary
GPT-OSS Deployment Documentation Update components/backends/trtllm/gpt-oss.md	Revised instructions to pull a prebuilt container image, added DYNAMO_CONTAINER_IMAGE variable, and included a collapsible section with manual build steps for ARM64 and x86_64 architectures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: Adjust the path to examples #2056: Updates documentation to prioritize using prebuilt container images, similar to this PR's restructuring.
• docs: fix issues in gpt-oss guide #2304: Adds the comprehensive gpt-oss.md guide; this PR modifies content introduced by that PR.
• docs: add GPT-OSS deployment guide #2297: Adds the initial GPT-OSS deployment guide; both PRs modify the same documentation file.

Poem

🐇
A container pulled with just one line,
No need to build—now isn’t that fine?
For ARM or x86, the choice is yours,
Collapsible secrets behind markdown doors.
Docs now simpler, less to compile—
This rabbit hops forward, with a smile!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

components/backends/trtllm/gpt-oss.md (1)

45-79: Minor build‐step inconsistencies

1. The x86_64 snippet omits --platform linux/amd64, which is helpful when building on non-x86 hosts (e.g. Apple M-series).
2. The two snippets reset DYNAMO_CONTAINER_IMAGE to different names (…-arm64, …-amd64) but later docker run relies on the value exported before the <details> block. Clarify that the subsequent docker run example assumes the pull workflow, or remind readers to export the new tag after a manual build.

Consider:

-# Build x86_64 image
-docker build -f container/Dockerfile.tensorrt_llm_prebuilt . \
+docker build --platform linux/amd64 -f container/Dockerfile.tensorrt_llm_prebuilt . \

and add a note:

After building, export DYNAMO_CONTAINER_IMAGE=<your custom tag> before continuing with Step 3.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bc3456b and 87d809d.

📒 Files selected for processing (1)

• components/backends/trtllm/gpt-oss.md (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Mirror Repository to GitLab
• GitHub Check: pre-merge-rust (.)
• GitHub Check: Build and Test - vllm