Open
Description
Description
When pushing an multiarch docker image, we can see in the gitea ui, the sha256 for each arch in the docker image.
The issue is when I click on a sha to see the detail, it gave me a 404 error.
The image can be pulled correctly and work like any other images.
This bug doesn't appear when the image is builded and pushed using docker buildx
Step to reproduce bad behaviour :
- On host A (arm64) :
docker build --push --platform arm64 -t try.gitea.io/cfouche/caddy-manifest:arm64 . - On host B (amd64) :
docker build --push --platform amd64 -t try.gitea.io/cfouche/caddy-manifest:amd64 . - On whatever host :
docker manifest create try.gitea.io/cfouche/caddy-manifest:latest try.gitea.io/cfouche/caddy-manifest:amd64 try.gitea.io/cfouche/caddy-manifest:arm64 && docker manifest push try.gitea.io/cfouche/caddy-manifest:latestordocker buildx imagetools create -t try.gitea.io/cfouche/caddy-manifest:latest try.gitea.io/cfouche/caddy-manifest:amd64 try.gitea.io/cfouche/caddy-manifest:arm64(same result)
Step to reproduce good behaviour :
- On whatever host :
docker buildx build --push --platform amd64 --platform arm64 -t try.gitea.io/cfouche/caddy-buildx:latest .
On both behaviour, the image worked, can be pulled on arm64 and amd64 host and have the correct manifest with the 2 arch
Gitea Version
v1.20.0-rc2
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Bad behaviour:
Capture vidéo du 2023-07-14 17-19-21.webm
Good behaviour:
Capture vidéo du 2023-07-14 18-42-49.webm
Git Version
No response
Operating System
Docker - Debian Host
How are you running Gitea?
Official Docker Image / https://try.gitea.io
Database
PostgreSQL