GHCR image tags missing 'v' prefix, inconsistent with GitHub Releases

[hwan515]

Description

There is an inconsistency between GitHub Release tag names and GHCR container image tags:

• GitHub Releases use v prefix: v0.55.1, v0.56.2, etc.
• GHCR image tags do NOT use v prefix: 0.55.1, 0.56.2, etc.

This causes confusion because users naturally look at the Releases page to find the version, then use that exact tag to pull the image — which fails.

Steps to Reproduce

# Fails — tag does not exist
docker pull ghcr.io/google/cadvisor:v0.55.1
# Error: ghcr.io/google/cadvisor:v0.55.1: not found

# Works — tag without 'v' prefix
docker pull ghcr.io/google/cadvisor:0.55.1

Impact

This has broken our CI/CD pipeline deployment. We suspect many other users may encounter the same issue, as using v-prefixed tags from releases is a very common convention.

Related issues:

• Missing docker image for v0.53.0 #3712 (Missing docker image for v0.53.0)
• Change from 0.54.0 -> 0.54.1 broke image name in metrics? #3807 (Change from 0.54.0 -> 0.54.1 broke image name)

Suggestion

Either:

1. Publish GHCR tags with both formats (v0.55.1 and 0.55.1) so both work, OR
2. Document the correct tag format in the README — clearly state that GHCR tags do NOT include the v prefix

I'm happy to submit a PR for option 2 if the maintainers prefer that approach.

[atirek89]

Facing same issue for other tags, 0.56.1 and 0.56.2

docker pull ghcr.io/google/cadvisor:v0.56.1
# Error: ghcr.io/google/cadvisor:v0.56.1: not found

# Works — tag without 'v' prefix
docker pull ghcr.io/google/cadvisor:0.56.1

# Fails — tag does not exist
docker pull ghcr.io/google/cadvisor:v0.56.2
# Error: ghcr.io/google/cadvisor:v0.56.2: not found

# Works — tag without 'v' prefix
docker pull ghcr.io/google/cadvisor:0.56.2