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

Content Length error when when retry happen on PUT #488

Open
joaopapereira opened this issue Feb 22, 2023 · 2 comments
Open

Content Length error when when retry happen on PUT #488

joaopapereira opened this issue Feb 22, 2023 · 2 comments
Labels
bug This issue describes a defect or unexpected behavior carvel accepted This issue should be considered for future work and that the triage process has been completed

Comments

@joaopapereira
Copy link
Member

What steps did you take:
Create a bundle very large and try to copy it to a registry like ACR.

What happened:

Executing command :  imgpkg [copy --bundle my.registry.io/my-bundle --to-tar /tmp/3150824826/bundle.tar]
Executing command :  imgpkg [copy --tar /tmp/3150824826/bundle.tar --to-repo my.azurecr.io/my-bundle]
2023/02/07 13:31:53 imgpkg: Error: Put "https://my.azurecr.io/v2/my-bundle/manifests/sha256-2d84dfb6d19ea5b2171d38acffb6fe5afb454de021d3ec0e92b40b327cbd8e1f.imgpkg": http:
  ContentLength=424 with Body length 0
exit status 1

What did you expect:
To successfully copy the bundle

Anything else you would like to add:
This issue contains the same problem. In the end was not solved.
To test out if adding the header would help, I created a version of imgpkg that just added the header has part of a transport and the error did not happen again.
This change might have to be done on ggcr to affect only the PUT method

Environment:

  • imgpkg version (use imgpkg --version): 0.35.0
  • Docker registry used (e.g. Docker HUB): ACR
  • OS (e.g. from /etc/os-release): all

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help work on this issue.

@joaopapereira joaopapereira added bug This issue describes a defect or unexpected behavior carvel triage This issue has not yet been reviewed for validity labels Feb 22, 2023
@github-actions
Copy link

github-actions bot commented Apr 4, 2023

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Apr 4, 2023
@joaopapereira joaopapereira added carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity stale This issue has had no activity for a while and will be closed soon labels Apr 4, 2023
@joaopapereira
Copy link
Member Author

Waiting on reply from ggcr

@renuy renuy moved this to Prioritized Backlog in Carvel Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes a defect or unexpected behavior carvel accepted This issue should be considered for future work and that the triage process has been completed
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

1 participant