Skip to content

Conversation

nv-anants
Copy link
Contributor

@nv-anants nv-anants commented Jul 28, 2025

Overview:

Copy whole dynamo repo into runtime container to run all pre-merge and mypy CI tests

Details:

ref: OPS-440

Summary by CodeRabbit

  • Chores
    • Streamlined the Docker image build process by consolidating file copying steps, resulting in improved efficiency and maintainability. No user-facing changes.

Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Walkthrough

This change updates the container/Dockerfile.vllm by consolidating several individual COPY commands into a single command that copies the entire /workspace/ directory from the ci_minimum stage into the runtime image. Associated comments are updated to reflect this consolidation and a TODO is added regarding future CI image plans.

Changes

Cohort / File(s) Change Summary
Dockerfile Workspace Copy Consolidation
container/Dockerfile.vllm
Replaces multiple COPY commands for specific directories with a single COPY of the entire workspace from ci_minimum; updates comments to explain rationale and future TODO.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~6 minutes

Possibly related PRs

Poem

🐇
One hop, one leap, the workspace goes,
From many copies to one that flows.
Docker builds now clean and neat,
With future plans not yet complete.
A single COPY, a rabbit’s delight—
CI will run, and all is 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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
container/Dockerfile.vllm (1)

467-469: COPY inside a RUN block is invalid Docker syntax – build will fail

COPY (and all other build-stage directives) must be a top-level instruction. Embedding it inside a shell if …; then in a RUN layer will cause Docker to error-out during parsing.

RUN if [ "$ARCH" = "arm64" ]; then \
    COPY --from=base /opt/vllm /opt/vllm; \
fi

The conditional copy can be expressed safely by splitting the stage or by copying unconditionally and relying on build-args for correctness.

- RUN if [ "$ARCH" = "arm64" ]; then \
-         COPY --from=base /opt/vllm /opt/vllm; \
-     fi
+# Copy vllm artifacts only for arm64 builds
+ARG ARCH
+COPY --from=base /opt/vllm /opt/vllm
+RUN if [ "$ARCH" != "arm64" ]; then rm -rf /opt/vllm; fi

Without this fix the image will not build.

🧹 Nitpick comments (1)
container/Dockerfile.vllm (1)

486-488: Whole-workspace copy bloats the runtime image & risks overwriting earlier layers

Pulling the entire /workspace/ from ci_minimum makes the runtime image several GB larger, ships all sources, build caches (target/, .mypy_cache/, etc.) and can mask/overwrite previously copied artefacts such as wheelhouse/ and metrics.

If the sole goal is to run mypy/pre-merge tests, consider:

  1. Creating a separate “ci-runtime” stage extending runtime just for CI.
  2. Copying only what static analysis needs, e.g.
    COPY --from=ci_minimum /workspace/{deploy,components,tests} /workspace/
  3. Using a .dockerignore in ci_minimum to strip large build artefacts before they reach this stage.

These changes keep the production runtime slim while still unblocking CI.

Is there any production workflow depending on the enlarged image size that we should account for?

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e82bc4e and 8f1cedc.

📒 Files selected for processing (1)
  • container/Dockerfile.vllm (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: nnshah1
PR: ai-dynamo/dynamo#1444
File: tests/fault_tolerance/scenarios.py:57-57
Timestamp: 2025-07-01T15:39:56.789Z
Learning: The fault tolerance tests in tests/fault_tolerance/ are designed to run only in the mounted container environment, so hardcoded absolute paths with `/workspace/` prefix are intentional and should not be changed to relative paths.
container/Dockerfile.vllm (1)

Learnt from: nnshah1
PR: #1444
File: tests/fault_tolerance/scenarios.py:57-57
Timestamp: 2025-07-01T15:39:56.789Z
Learning: The fault tolerance tests in tests/fault_tolerance/ are designed to run only in the mounted container environment, so hardcoded absolute paths with /workspace/ prefix are intentional and should not be changed to relative paths.

⏰ 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). (1)
  • GitHub Check: Build and Test - vllm

@nv-anants nv-anants enabled auto-merge (squash) July 28, 2025 19:42
@nv-anants nv-anants merged commit ca0035f into main Jul 28, 2025
11 of 12 checks passed
@nv-anants nv-anants deleted the anants/mypy branch July 28, 2025 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants