[Feature] Add OCI Image Annotations to container images

[JMonde]

Summary

This PR adds standard OCI Image Annotations to all vLLM Dockerfiles, improving container image metadata for registries and tooling.

Changes

Added OCI-compliant LABEL instructions to the following Dockerfiles:

• Dockerfile (CUDA) - org.opencontainers.image.* annotations
• Dockerfile.cpu - Enhanced existing annotations with complete OCI spec
• Dockerfile.rocm - Added full OCI annotations
• Dockerfile.xpu - Added full OCI annotations
• Dockerfile.ppc64le - Added full OCI annotations

Annotations Added

Each image now includes:

Annotation	Value
org.opencontainers.image.title	vLLM [variant]
org.opencontainers.image.description	Platform-specific description
org.opencontainers.image.url	https://vllm.ai
org.opencontainers.image.source	https://github.com/vllm-project/vllm
org.opencontainers.image.vendor	vLLM Project
org.opencontainers.image.licenses	Apache-2.0

Benefits

1. Registry Integration: Container registries (GHCR, Docker Hub, ECR, etc.) can display rich metadata
2. Security & Compliance: Automated tools can verify source and license information
3. SBOM Generation: Software Bill of Materials tools use OCI annotations for provenance
4. Discoverability: Better search and categorization in container registries
5. Standards Compliance: Follows OCI Image Format Specification v1.0

Example

After building, the image metadata will show:

$ docker inspect vllm/vllm-openai:latest | jq '.[0].Config.Labels'
{
  "org.opencontainers.image.title": "vLLM",
  "org.opencontainers.image.description": "A high-throughput and memory-efficient inference and serving engine for LLMs",
  "org.opencontainers.image.url": "https://vllm.ai",
  "org.opencontainers.image.source": "https://github.com/vllm-project/vllm",
  "org.opencontainers.image.vendor": "vLLM Project",
  "org.opencontainers.image.licenses": "Apache-2.0"
}

Related

Fixes: #32674

[gemini-code-assist]

Code Review

This pull request introduces standard OCI image annotations to all vLLM Dockerfiles, which is a great improvement for image metadata and tooling integration. The changes are consistent across the different Dockerfiles. However, I've identified a high-severity issue where the labels defined in docker/docker-bake.hcl will override the new annotations in docker/Dockerfile during bake builds, leading to inconsistent metadata. My review includes a comment to address this discrepancy.

[gemini-code-assist]

While these labels are a great addition for standard docker build commands, they will be overridden by the labels defined in docker/docker-bake.hcl when using docker buildx bake. The labels in docker-bake.hcl are currently inconsistent with the changes in this PR.

Specifically, in docker/docker-bake.hcl:

• org.opencontainers.image.url is missing.
• org.opencontainers.image.vendor is set to "vLLM" instead of "vLLM Project".
• org.opencontainers.image.description has a vLLM: prefix that is not present here.

To ensure consistency across all build methods, please update the _labels target in docker/docker-bake.hcl to match these new annotations. This will ensure that bake builds have the same rich metadata.

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @JMonde.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @JMonde.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork