github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Error 404 on container image sha when using manifest list #11229

New Issue
Closed
opened 2025-11-02 09:31:29 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:31:29 -06:00
Owner
Copy Link

Originally created by @cfouche3005 on GitHub (Jul 14, 2023).

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:latest or docker 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

Originally created by @cfouche3005 on GitHub (Jul 14, 2023). ### 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](https://try.gitea.io/cfouche/-/packages/container/caddy-manifest/sha256:124a9639c034cd449d2a299069025ae84da7dfeb9421eefb85098806ef4fea18) 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](https://try.gitea.io/cfouche/-/packages/container/caddy-manifest/latest) : - 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:latest` or `docker 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](https://try.gitea.io/cfouche/-/packages/container/caddy-buildx/latest) : - 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](https://try.gitea.io/cfouche/-/packages/container/caddy-manifest/latest): [Capture vidéo du 2023-07-14 17-19-21.webm](https://github.com/go-gitea/gitea/assets/51720655/524b0b53-f140-4fed-a77c-d14e7a6581f1) [Good behaviour](https://try.gitea.io/cfouche/-/packages/container/caddy-buildx/latest): [Capture vidéo du 2023-07-14 18-42-49.webm](https://github.com/go-gitea/gitea/assets/51720655/c603e1e0-8d3d-4056-9f3f-49f0be668d6e) ### Git Version _No response_ ### Operating System Docker - Debian Host ### How are you running Gitea? Official Docker Image / https://try.gitea.io ### Database PostgreSQL
GiteaMirror added the topic/packagestype/bug labels 2025-11-02 09:31:29 -06:00
GiteaMirror commented 2025-11-02 09:31:30 -06:00
Author
Owner
Copy Link

@cfouche3005 commented on GitHub (Jul 17, 2023):

Still present on 1.20.0 (and try.gitea.io version 1.21.0+dev-305-g8bb0a03ea)

@cfouche3005 commented on GitHub (Jul 17, 2023): Still present on 1.20.0 (and try.gitea.io version 1.21.0+dev-305-g8bb0a03ea)
GiteaMirror commented 2025-11-02 09:31:30 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 1, 2025):

Related to #26839

I think the problem should have been fixed on main branch, feel free to try the nightly build.

If there is still any problem, feel free to reopen and/or provide some reproducible steps.

Thank you all.

@wxiaoguang commented on GitHub (Jul 1, 2025): Related to #26839 I think the problem should have been fixed on main branch, feel free to try the nightly build. * https://dl.gitea.com/gitea/main-nightly/ * https://hub.docker.com/r/gitea/gitea/tags?name=nightly If there is still any problem, feel free to reopen and/or provide some reproducible steps. Thank you all.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/packages type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?