Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pushing large image to registry results in Error: writing blob: uploading layer chunked: StatusCode: 499, "Client Closed Request" #52

Closed
tepene opened this issue May 25, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@tepene
Copy link
Collaborator

tepene commented May 25, 2024

Describe the bug

The build job is also pushing the image to registry. This steps fails with Error: writing blob: uploading layer chunked: StatusCode: 499, "Client Closed Request" when the image is quite large, like bluefin.

What did you expect to happen?

Pushing image should not result in error. No matter what the size

Extra information or context

No response

@tepene tepene added the bug Something isn't working label May 25, 2024
@tepene tepene self-assigned this May 25, 2024
@tepene
Copy link
Collaborator Author

tepene commented May 25, 2024

Might be related to the resources limits in the pod configuration. But after disabling them i get write tcp 127.0.0.1:43412->127.0.0.1:443: write: broken pipe.
port 443 is mapped to traefik reverse proxy. Might be an issue there

@tepene
Copy link
Collaborator Author

tepene commented May 25, 2024

added the label traefik.http.serverstransports.registry.forwardingtimeouts.dialTimeout: "900s" to the registry container. Upload worded. Default dialTimout is 30s, i hope 900s is safe enough.

Source: https://doc.traefik.io/traefik/routing/services/#forwardingtimeouts

tepene added a commit that referenced this issue May 26, 2024
trying to avoid 'StatusCode: 499, Client Closed Request'
@tepene
Copy link
Collaborator Author

tepene commented May 27, 2024

I removed the label traefik.http.serverstransports.registry.forwardingtimeouts.dialTimeout: "900s" since it also worked without it. After re-configuring the build_project.yml playbook the jobs were running ok.
Closing here and will re-open if need be.

@tepene tepene closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant