when pushing multiple architecture and os of the same container package, the registry override image with the latest.

[ArKam]

Description

Hi team,

I was pushing a container to the container registry as a feature test, when I found out that the registry doesn't support storing a container image for different architecture using the same image name.

If you build an image for both, linux/arm64 and linux/x86_64 or windows/arm64 and windows/x86_64 and try to push each resulting image to the container registry, the latest build will override the previous package.

With docker hub or quay or ghcr, you can have the same URL: forge.domain.tld/owner/package:version that deliver container version depending on the client spec (arm/x86_64) in here, from my understanding and test so far, I'll have to create an image with a name that specify <image_name>-arm64 or <image_name>-x86_64.

Gitea Version

1.22.2

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

provided by gitea/gitea:1.22.2

Operating System

linux

How are you running Gitea?

Using kubernetes to deploy gitea/gitea:1.22.2 release.

Database

PostgreSQL