Docker images generating when not needed due to bug

[PhilETaylor]

What happened?

Sorry me again

I noticed that my daily update tasks downloaded a new docker image again today so I went investigating...

it seems that the PR to fix the image confusion is now resulting in errors in the scheduled action "Check PHP versions" task

time="2025-07-13T04:13:38Z" level=fatal msg="Error parsing image name \"docker://docker.io/dunglas/frankenphp:v1.8.0-php8.2\": reading manifest v1.8.0-php8.2 in docker.io/dunglas/frankenphp: manifest unknown"
time="2025-07-13T04:13:38Z" level=fatal msg="Error parsing image name \"docker://docker.io/dunglas/frankenphp:v1.8.0-php8.3\": reading manifest v1.8.0-php8.3 in docker.io/dunglas/frankenphp: manifest unknown"
time="2025-07-13T04:13:38Z" level=fatal msg="Error parsing image name \"docker://docker.io/dunglas/frankenphp:v1.8.0-php8.4\": reading manifest v1.8.0-php8.4 in docker.io/dunglas/frankenphp: manifest unknown"

This is causing the images to be built repeatedly (when the schedule runs daily - and probably costs money?) when they are not needed to be. (hope I explained that clearly?)

//cc @AlliBalliBaba

I think the issue is the v in the tag name...

~ docker pull dunglas/frankenphp:v1.8.0-php8.4
Error response from daemon: manifest for dunglas/frankenphp:v1.8.0-php8.4 not found: manifest unknown: manifest unknown

~ docker pull dunglas/frankenphp:1.8.0-php8.4
1.8.0-php8.4: Pulling from dunglas/frankenphp
Digest: sha256:751f6291c1a41f3b1705778b2db6f2e1134dc2969532a8aa47692eea333dff11
Status: Image is up to date for dunglas/frankenphp:1.8.0-php8.4
docker.io/dunglas/frankenphp:1.8.0-php8.4

The v is coming from the

FRANKENPHP_LATEST_TAG=$(gh release view --repo php/frankenphp --json tagName --jq '.tagName')

which gives the v1.8.0

[AlliBalliBaba]

Ah yeah you're right, the 'v' should be removed or else it will detect new versions daily, thanks for investigating!

(this does not cost money,.it's about being more efficient)

[PhilETaylor]

(this does not cost money,.it's about being more efficient)

I was referring to GitHub Actions running nightly building the images when they don't need to - which do cost money :)