[docker] feat: upgrade vllm, TE and megatron version

[ETOgaosion]

What does this PR do?

upgrade vllm (0.24.0) and megatron (core_v0.18.0) version

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include fsdp, megatron, veomni, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data, cfg, reward, fully_async, one_step_off
  • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...
• Once your PR is ready for CI, send a message in the ci-request channel in the verl Slack workspace. (If not accessible, please try the Feishu group (飞书群).)
• If your PR is related to the recipe submodule, please also update the reference to the submodule commit via git submodule update --remote or cd recipe && git pull origin main.

[gemini-code-assist]

Code Review

This pull request updates the Dockerfiles for SGLang and vLLM to parameterize the megatron-bridge version and simplifies the vLLM installation by using pip instead of building from source. The feedback highlights that the vllm-omni package version is hardcoded to 0.24.0 in the vLLM Dockerfile instead of utilizing the newly introduced VLLM_OMNI_VERSION build argument.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[wuxibin89]

@HollowMan6 Can we remove all on-fly megatron-bridge and megatron installation now?

[HollowMan6]

Yes if we have the expected megatron-bridge and megatron-lm installed in the container image.

[HollowMan6]

I think we can remove all on-fly megatron-bridge and megatron installation and run the CI to see if there's any issue.

[ETOgaosion]

Megatron Bridge/TransferQueue will be built in with this image.

[ETOgaosion]

transformers is troublesome, we will not force single version transformers work with verl, we shall built in with image, and accelerate uv integration to handle conflicts.