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

Client Closed Request when pushing docker container to gitea #13372

New Issue
Closed
opened 2025-11-02 10:40:18 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 10:40:18 -06:00
Owner
Copy Link

Originally created by @TheZoker on GitHub (Aug 7, 2024).

Description

When I try to push a docker image via gitea actions to the gitea container repo, I get this error:

#14 pushing layer 408568b8af61 725.15MB / 725.15MB 358.6s done
#14 pushing layer 0ae121d8b283 358.6s done
#14 pushing layer 5a110aa3f10d 358.6s done
#14 pushing layer ef352e7cbd50 358.6s done
#14 pushing layer 78561cef0761 358.6s done
#14 ERROR: unknown: Client Closed Request
------
 > pushing git.domain.com/user/project:main with docker:
------
ERROR: unknown: Client Closed Request
::group::Reference
default/default/ycrwvrjlj5jflhfak0nmeos96
::endgroup::
::group::Check build summary support
::warning::Build summary is not yet supported on GHES
::endgroup::
::error::buildx failed with: ERROR: unknown: Client Closed Request

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.zkr.dev/FlorianGareis/ef5a9912289743689b72bf949eceba81

Screenshots

image

Git Version

2.45.2

Operating System

Proxmox LXC

How are you running Gitea?

Docker compose file

Database

SQLite

Originally created by @TheZoker on GitHub (Aug 7, 2024). ### Description When I try to push a docker image via gitea actions to the gitea container repo, I get this error: ``` #14 pushing layer 408568b8af61 725.15MB / 725.15MB 358.6s done #14 pushing layer 0ae121d8b283 358.6s done #14 pushing layer 5a110aa3f10d 358.6s done #14 pushing layer ef352e7cbd50 358.6s done #14 pushing layer 78561cef0761 358.6s done #14 ERROR: unknown: Client Closed Request ------ > pushing git.domain.com/user/project:main with docker: ------ ERROR: unknown: Client Closed Request ::group::Reference default/default/ycrwvrjlj5jflhfak0nmeos96 ::endgroup:: ::group::Check build summary support ::warning::Build summary is not yet supported on GHES ::endgroup:: ::error::buildx failed with: ERROR: unknown: Client Closed Request ``` ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.zkr.dev/FlorianGareis/ef5a9912289743689b72bf949eceba81 ### Screenshots ![image](https://github.com/user-attachments/assets/50eaf44b-ae11-4100-8ded-58b42028007b) ### Git Version 2.45.2 ### Operating System Proxmox LXC ### How are you running Gitea? Docker compose file ### Database SQLite
GiteaMirror added the topic/packagesissue/needs-feedback labels 2025-11-02 10:40:18 -06:00
GiteaMirror commented 2025-11-02 10:40:19 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 7, 2024):

The log does not contain the Docker requests.

@KN4CK3R commented on GitHub (Aug 7, 2024): The log does not contain the Docker requests.
GiteaMirror commented 2025-11-02 10:40:19 -06:00
Author
Owner
Copy Link

@TheZoker commented on GitHub (Aug 7, 2024):

Ah sorry, this should include the logs from the gitea runner:
https://gist.zkr.dev/FlorianGareis/ac95262431dc41cd9c30d65bf8de11b9

@TheZoker commented on GitHub (Aug 7, 2024): Ah sorry, this should include the logs from the gitea runner: https://gist.zkr.dev/FlorianGareis/ac95262431dc41cd9c30d65bf8de11b9
GiteaMirror commented 2025-11-02 10:40:20 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 8, 2024):

Need the server log with the docker requests.

@KN4CK3R commented on GitHub (Aug 8, 2024): Need the server log with the docker requests.
GiteaMirror commented 2025-11-02 10:40:20 -06:00
Author
Owner
Copy Link

@heryTz commented on GitHub (Aug 9, 2024):

I also encountered the same problem.

The error occurs on all large 400Mb images

2024/08/09 11:53:25 ...ntainer/container.go:90:apiError() [E] unexpected EOF
2024/08/09 11:53:25 ...eb/routing/logger.go:102:func1() [I] router: completed PATCH /v2/agst/front-test-staging/blobs/uploads/174sx9oojjiugutlhrgwog7dr for xx.xxx.xx.xxx:57996, 500 Internal Server Error in 50805.1ms @ container/container.go:328(container.UploadBlob)

Here is the complete log :
gitea.log

@heryTz commented on GitHub (Aug 9, 2024): I also encountered the same problem. The error occurs on all large 400Mb images ``` 2024/08/09 11:53:25 ...ntainer/container.go:90:apiError() [E] unexpected EOF 2024/08/09 11:53:25 ...eb/routing/logger.go:102:func1() [I] router: completed PATCH /v2/agst/front-test-staging/blobs/uploads/174sx9oojjiugutlhrgwog7dr for xx.xxx.xx.xxx:57996, 500 Internal Server Error in 50805.1ms @ container/container.go:328(container.UploadBlob) ``` Here is the complete log : [gitea.log](https://github.com/user-attachments/files/16560845/gitea.log)
GiteaMirror commented 2025-11-02 10:40:20 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 9, 2024):

Maybe your proxy has a upload limit, not a Gitea problem.

@KN4CK3R commented on GitHub (Aug 9, 2024): Maybe your proxy has a upload limit, not a Gitea problem.
GiteaMirror commented 2025-11-02 10:40:20 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Oct 19, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Oct 19, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
GiteaMirror commented 2025-11-02 10:40:20 -06:00
Author
Owner
Copy Link

@leikoilja commented on GitHub (Dec 30, 2024):

came across similar issue, one of the blobs (313mb) was constantly failing to be pushed over the WiFI. I looked at increasing traefik proxy timeouts, headers, payload sizes etc...
at the end of the day - it was 💩 internet connection, so moving closer to the router and running speedtest to find the bets coverage (mobile vs wifi) has helped and on the 2nd attempt succeeded to upload 😮‍💨

@leikoilja commented on GitHub (Dec 30, 2024): came across similar issue, one of the blobs (313mb) was constantly failing to be pushed over the WiFI. I looked at increasing traefik proxy timeouts, headers, payload sizes etc... at the end of the day - it was 💩 internet connection, so moving closer to the router and running speedtest to find the bets coverage (mobile vs wifi) has helped and on the 2nd attempt succeeded to upload 😮‍💨
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 issue/needs-feedback topic/packages
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#13372
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?