Content Length error when when retry happen on PUT
Opened this issue · 2 comments
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.
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.
Waiting on reply from ggcr