Codeberg/Community
54
325
Fork
You've already forked Community
12

500 Internal Server Error on multiarch docker container package upload #1747

Open
opened 2025年01月04日 00:24:16 +01:00 by karlpip · 3 comments

Comment

Dear codeberg team,

i assume that this is a issue related to codeberg rather than forgejo, if not please excuse me, I'll reopen this at forgejo.

I recently tried to push an docker image build with https://codeberg.org/karlpip/akustik/src/branch/main/Dockerfile to codeberg.org/karlpip/akustik:v0.1.0. The following error happened:

The push refers to repository [codeberg.org/karlpip/akustik]
76f69431dd2e: Pushed
d3b1c1d96f7d: Pushed
38a8310d387e: Pushed
failed commit on ref "manifest-sha256:fa59a63c2eb40f51281b2dc780bed830e6dee0c1c3eed6e1cacbf1c4e76cef9b": unexpected status from PUT request to https://codeberg.org/v2/karlpip/akustik/manifests/v0.1.0: 500 Internal Server Error

The bug is reproducible, if i delete the broken package on codeberg and retry the same error occurs again. Maybe this is related to the fact that i've build this image for 2 architectures with docker build --platform linux/amd64,linux/arm64 -t akustik:v0.1.0 ..

Thanks for your attention

### Comment Dear codeberg team, i assume that this is a issue related to codeberg rather than forgejo, if not please excuse me, I'll reopen this at forgejo. I recently tried to push an docker image build with https://codeberg.org/karlpip/akustik/src/branch/main/Dockerfile to codeberg.org/karlpip/akustik:v0.1.0. The following error happened: ``` The push refers to repository [codeberg.org/karlpip/akustik] 76f69431dd2e: Pushed d3b1c1d96f7d: Pushed 38a8310d387e: Pushed failed commit on ref "manifest-sha256:fa59a63c2eb40f51281b2dc780bed830e6dee0c1c3eed6e1cacbf1c4e76cef9b": unexpected status from PUT request to https://codeberg.org/v2/karlpip/akustik/manifests/v0.1.0: 500 Internal Server Error ``` The bug is reproducible, if i delete the broken package on codeberg and retry the same error occurs again. Maybe this is related to the fact that i've build this image for 2 architectures with ```docker build --platform linux/amd64,linux/arm64 -t akustik:v0.1.0 .```. Thanks for your attention

Hi,

What are the commands you're using to push the image?

Hi, What are the commands you're using to push the image?
Author
Copy link

Good morning,

i am using docker push codeberg.org/karlpip/akustik:v0.1.0 after tagging it with docker tag akustik:v0.1.0 codeberg.org/karlpip/akustik:v0.1.0

Good morning, i am using `docker push codeberg.org/karlpip/akustik:v0.1.0` after tagging it with `docker tag akustik:v0.1.0 codeberg.org/karlpip/akustik:v0.1.0`

I thought this was an easy fix but it seems like a bigger issue with using a manifest list (which I don't know enough of to go ahead and fix), there are reports in Gitea about this specific problem: https://github.com/go-gitea/gitea/issues/26839 & https://github.com/go-gitea/gitea/issues/25893. No associated issue in Forgejo for this. The internal server error is likely stemming from some remnant data in the database that is caused by this bug.

I thought this was an easy fix but it seems like a bigger issue with using a manifest list (which I don't know enough of to go ahead and fix), there are reports in Gitea about this specific problem: https://github.com/go-gitea/gitea/issues/26839 & https://github.com/go-gitea/gitea/issues/25893. No associated issue in Forgejo for this. The internal server error is likely stemming from some remnant data in the database that is caused by this bug.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1747
Reference in a new issue
Codeberg/Community
No description provided.
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?