build: bump vllm-openai-cpu base image to v0.25.0

[nathan-weinberg]

Summary

• Bumps the vLLM CPU base image from v0.23.0 to v0.25.0 in vllm/Containerfile

Test plan

• CI builds the vLLM CPU container image successfully
• Smoke tests pass against the new vLLM version
• Integration tests pass

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the application’s container image to use the newer vLLM CPU runtime version 0.25.0.
  • Existing model setup and serving behavior remain unchanged.

[coderabbitai]

📝 Walkthrough

Walkthrough

The vllm/Containerfile base image is updated from vllm/vllm-openai-cpu:v0.23.0 to vllm/vllm-openai-cpu:v0.25.0. No other build instructions or runtime behavior change.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: bumping the vllm-openai-cpu base image to v0.25.0.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Contribution Quality And Spam Detection	✅ Passed	Single-file base-image bump; no second-category signal of spam or security theater beyond a routine PR template.
No Hardcoded Secrets	✅ Passed	No hardcoded secrets, embedded creds, or long base64 found; vllm/Containerfile only uses a BuildKit secret mount (not a literal secret).
No Weak Cryptography	✅ Passed	vllm/Containerfile only bumps a base image tag; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found (CWE-327/CWE-208).
No Injection Vectors	✅ Passed	Only a Docker base-image tag changed; no new CWE-89/78/94/502/79 injection patterns were introduced in the PR diff.
No Privileged Containers	✅ Passed	vllm/Containerfile only bumps the base image; it sets USER 1001 and has no privileged flags, host settings, or root-user directives.
No Sensitive Data In Logs	✅ Passed	Only change is a base-image tag bump in vllm/Containerfile; no logging statements or sensitive-data emissions found, so no CWE-532 exposure.

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@vllm/Containerfile`:
- Line 5: Update the Containerfile’s FROM declaration to pin
vllm/vllm-openai-cpu to its immutable manifest digest, replacing the mutable
v0.25.0 tag while preserving the selected image.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 7141cefd-6f41-4216-a327-dc46e52845be

📥 Commits

Reviewing files that changed from the base of the PR and between f166d44 and ac25523.

📒 Files selected for processing (1)

• vllm/Containerfile

[coderabbitai]

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Containerfile =="
git ls-files -- vllm/Containerfile
wc -l vllm/Containerfile
cat -n vllm/Containerfile | sed -n '1,40p'

echo "== Any digest-pinned vllm base image references =="
rg -n --no-heading 'FROM\s+vllm/vllm-openai-cpu:.*`@sha256`:|FROM\s+vllm/vllm-openai-cpu:[^[:space:]]+' vllm/Containerfile .github . || true

Repository: opendatahub-io/ogx-distribution

Length of output: 1965

---

Pin the vLLM base image by digest.

vllm/vllm-openai-cpu:v0.25.0 is a mutable supply-chain boundary; a retagged image or compromised publish path can silently change the runtime contents (CWE-494). Lock it to the manifest digest instead of the tag.

Patch

-FROM vllm/vllm-openai-cpu:v0.25.0
+FROM vllm/vllm-openai-cpu:v0.25.0@sha256:<manifest-digest>

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@vllm/Containerfile` at line 5, Update the Containerfile’s FROM declaration to
pin vllm/vllm-openai-cpu to its immutable manifest digest, replacing the mutable
v0.25.0 tag while preserving the selected image.

Source: Path instructions

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[rhods-ci-bot]

@nathan-weinberg: The following test has Succeeded:

OCI Artifact Browser URL

View in Artifact Browser

Inspecting Test Artifacts Manually

To inspect your test artifacts manually, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/opendatahub/odh-ci-artifacts:ogx-core-functional-its-zmpt8