Description

I build and push architecture-specific container images to Gitea's container registry and then create a manifest to combine them all into one multi-architecture tag and push that manifest as the image I expect users to actually use.

It appears that when I do this, Gitea creates duplicate packages for them under their sha instead of referencing the existing packages. When I push out a new version of all my tags and manifest, those packages that are listed just by their naked sha hashes are left still there. They are not visible in the normal Packages section of the web ui for any user or organization unless I delete all the named tags/versions first. They are visible in the Package Management section of the site administrative UI though and only in that interface can I see that I have literally thousands of old unreferenced container images that Gitea thinks are still active.

These do not seem to be cleaned up or deleted by Gitea. The UI doesn't provide a means to delete them aside from one-by-one either which makes cleaning this up an extremely daunting task it would seem. Is there a) a way to stop this from continuing to happen aside from "don't use manifests" and b) any way to batch delete container packages?

Gitea Version

1.22.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

alpine-s6:edge is a manifest containing the tags for amd64, x86, aarch64, armv7, and riscv64 architectures. I have drawn connections showing which packages are duplicates of one another.

Git Version

No response

Operating System

Alpine v3.20

How are you running Gitea?

self-built docker container

Database

SQLite