chore: update sgl version and fix h100 wideep example

[ishandhanani]

Summary by CodeRabbit

• Chores
  • Updated the sglang container to use a newer version of the sglang dependency.
  • Modified the sglang-wideep container to always use the latest version of the dynamo repository from its default branch, instead of a fixed commit.

[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

This change updates two Dockerfiles: one updates the SGLANG_VERSION argument to a newer patch version, and the other removes a fixed commit hash from the dynamo repository clone, defaulting to the latest branch state and simplifying the clone step.

Changes

Cohort / File(s)	Change Summary
SGLANG Version Bump container/Dockerfile.sglang	Updates the SGLANG_VERSION build argument from "0.4.9.post1" to "0.4.9.post6".
Dynamo Clone Simplification container/Dockerfile.sglang-wideep	Removes fixed commit hash for dynamo repo; clones the latest state from the default branch and removes related ARG and checkout steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: bump sgl and update dp attn yaml #1362: Updates the version or commit of the sglang dependency in the Dockerfile, similar to the version bump in this PR.
• build: minor improvements to sglang dockerfile #1917: Also updates container/Dockerfile.sglang to use a newer sglang version, focusing on Dockerfile improvements.
• build: Add support for sglang runtime image #1770: Modifies the same Dockerfile but introduces a new sglang runtime image; both PRs affect sglang Dockerfile setup.

Poem

In Docker’s warren, versions hop along,
SGLANG grows stronger, its patch notes a song.
Dynamo now fetches the freshest of code,
No more old hashes to burden the load.
With each little change, our container’s delight—
The rabbits rejoice, for the build is just right! 🐇

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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 358e908 and c938319.

📒 Files selected for processing (2)

• container/Dockerfile.sglang (1 hunks)
• container/Dockerfile.sglang-wideep (1 hunks)

🔇 Additional comments (1)

container/Dockerfile.sglang (1)

168-175: Unable to locate upstream tag v0.4.9.post6

The git checkout v${SGLANG_VERSION} step in container/Dockerfile.sglang (lines 168–175) will fail if the tag isn’t present. I ran:

git ls-remote --tags https://github.com/sgl-project/sglang.git | grep "refs/tags/v0.4.9.post6$"

and didn’t find a matching tag. Please verify that v0.4.9.post6 exists in the upstream repo (or push/update it), or adjust SGLANG_VERSION to a valid tag before merging.

[nv-anants]

/ok to test 06ce5bd

[ishandhanani]

/ok to test d819879

[biswapanda]

LGTM with a comment to pin version