Skip to content

chore(deps): update vllm/vllm-openai docker tag to v0.9.1 #4106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wanghe-fit2cloud merged 2 commits into from
Jun 11, 2025
Merged

chore(deps): update vllm/vllm-openai docker tag to v0.9.1 #4106

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
40e2d20
chore(deps): update vllm/vllm-openai docker tag to v0.9.1
renovate[bot] Jun 11, 2025
36e67b8
Update app version [skip ci]
Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 apps/vllm/0.9.0/data.yml → apps/vllm/0.9.1/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/vllm/0.9.0/docker-compose.yml → apps/vllm/0.9.1/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
vllm:
image: vllm/vllm-openai:v0.9.0
image: vllm/vllm-openai:v0.9.1
container_name: ${CONTAINER_NAME}
restart: always
runtime: nvidia
Copy link
Copy Markdown
Member

@wanghe-fit2cloud wanghe-fit2cloud Jun 11, 2025

Choose a reason for hiding this comment

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

The provided diff shows an update from vllm/vllm-openai:v0.9.0 to vllm/vllm-openai:v0.9.1. This is typically a version upgrade from one release of the service to another, which is usually beneficial for bug fixes and improvements.

Potential issues or considerations:

  1. Version Compatibility: Ensure that both versions of VLLM are compatible with each other and with any dependencies.

  2. Environment Variables: Check if the ${CONTAINER_NAME} environment variable exists and has been properly defined in your deployment settings or configuration file.

  3. Caching and Rebuilds: If you have caching mechanisms in place, it might be beneficial to clear them after updating to avoid using outdated images during deployments.

Optimization suggestions:

  • Monitoring: Consider setting up monitoring tools to track performance metrics (RAM usage, GPU utilisation) on the updated containers running on NVIDIA GPUs to ensure they meet performance expectations.
  • Testing: Always test updates thoroughly in a staging environment before deploying them to production to prevent any unexpected downtime or issues.
  • Backup Plan: Maintain backup procedures in case there's a rollback needed due to compatibility or stability concerns.

Overall, this change introduces only a software update to address potential issues and includes best practice recommendations for managing and testing such changes effectively.

Copy link
Copy Markdown
Member

@wanghe-fit2cloud wanghe-fit2cloud Jun 11, 2025

Choose a reason for hiding this comment

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

The code difference is that it has changed the version of the VLLM Docker image from v0.9.0 to v0.9.1. This update may include bug fixes, new features, or performance improvements, depending on the changes made in this newer version.

No other issues were identified, assuming only this change was necessary and appropriate for your use case.

Expand Down