Skip to content

Pin the vLLM quick start to a Dynamo revision that imports on the pinned vLLM nightly - #160

Merged
luckyq merged 1 commit into
mainfrom
doxu/quickstart-dynamo-pin
Nov 3, 2026
Merged

luckyq merged 1 commit into
mainfrom
doxu/quickstart-dynamo-pin

Conversation

@luckyq

@luckyq luckyq commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

Problem

Fix

  • DYNAMO_REF → 318ab039 (Dynamo main, 2026-11-02). Dynamo dropped the renamed import on 2026-10-23 (build(vllm): bump core to v0.32.0 and Omni to v0.32.0rc1 dynamo#16757); v1.6.0 and v1.6.1 both still have it. VLLM_IMAGE and KVCR_VLLM_REF are unchanged.
  • The compatibility check now also runs import dynamo.vllm.main, so a Dynamo/vLLM pair that cannot start a worker fails the build instead of the first python -m dynamo.vllm.

Validation

  • Image built from this Dockerfile unchanged otherwise (ghcr.io/luckyq/kvcr-phase1:qs-218c7816b34b, 7 min); the new import check passes.
  • 2×H100 (dynamo-aws-dev-02), Qwen3-8B, Guard mode, Phase 1 harness TC-01/02/03: 3/3 PASS (source_write == remote_deliver, 0 token mismatches).
  • Same Dynamo revision with the full matrix earlier today: dense 6/6, 2P+1D 6/6, Qwen3.5-4B hybrid 6/6.

Fixes #159.

…ned vLLM nightly

Signed-off-by: doxu <doxu@nvidia.com>
@luckyq
luckyq merged commit 5ce23b1 into main Nov 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dockerfile.quick-start-vllm (v0.2.0): pinned Dynamo v1.6.0 cannot import on the pinned vLLM nightly

2 participants