Docker image not available

[hiaw]

Branch

main

Branch (if other)

No response

Version / Tag / Commit

latest

Provider(s) Affected

No response

Deployment Method

Docker

Operating System

macOS 26.2

Python Version (if running from source)

No response

Bug Description

When I ran docker pull ghcr.io/mirrowel/llm-api-key-proxy:latest I got the following error.
Error response from daemon: manifest unknown

When I ran docker pull ghcr.io/mirrowel/llm-api-key-proxy:dev-latest, it works fine.

The documentation instruction is to use latest instead of dev-latest. So if you can can fix the tag/manifest it'll be great. Thanks.

Steps to Reproduce

ran docker pull ghcr.io/mirrowel/llm-api-key-proxy:latest

Expected Behavior

latest: Pulling from mirrowel/llm-api-key-proxy
d6...............: Pull complete
62...............: Pull complete
..........
Digest: sha256:6d..........................................
Status: Downloaded newer image for ghcr.io/mirrowel/llm-api-key-proxy:latest
ghcr.io/mirrowel/llm-api-key-proxy:latest

Actual Behavior

Error response from daemon: manifest unknown

Error Logs / Messages

Error response from daemon: manifest unknown

Pre-submission Checklist

• I have searched existing issues to ensure this is not a duplicate

[Mirrowel]

@SSinist3r wanna take up fixing up the docker stuff? as i said previously - not an expert.

[mirrobot-agent]

@hiaw Thank you for submitting this issue. I am now beginning my analysis and will report back shortly.

[Mirrowel]

Gemini really is stupid and just didn't post the finding. Hate gemini.
"While there is an ignore-versions: ".*latest.*" rule, it appears to be ineffective for GHCR images in the actions/delete-package-versions@v5 action (likely matching against the version digest rather than the associated tags), leading to the deletion of the latest tag once it falls out of the top 20 most recent versions."