imgpkg miscalculates apache/nifi copy, produces corrupt image layer when copying apache/nifi in a bundle

[TheBritz]

Miscalculation during copy

What steps did you take:

1. Ran imgpkg copy -i on apache/nifi

imgpkg copy -i apache/nifi:latest --to-repo my.registry.com/docker/apache/nifi

What happened:

• imgpkg calculates an incorrect copy size (much too small)
• copy progress continues past 100% to >1000% for a total of ~2GB
• despite size and progress calculations, copy succeeds
  • copied image can be pulled via docker cli

What did you expect:

• imgpkg correctly calculates image size and represents image copy progress

Corrupt image layer when copying in a bundle

What steps did you take:

1. Create an image bundle that includes apache/nifi
2. Publish image bundle
3. Copy image bundle to a different registry

imgpkg copy -b my.registry.com/docker/apache/nifi-bundle:latest --to-repo my.registry2.com/docker/apache/nifi-bundle

What happened:

• imgpkg calculates an incorrect copy size (much like when copying the direct image)
• copy progress does not continue past 100%
• copy indicates success
• Image cannot be successfully pulled via docker cli
  • Attempting to pull will resort in a filesystem layer verification failed for digest <sha256> error

Environment:

• imgpkg version (use imgpkg --version): 0.39.0
• Docker registry used (e.g. Docker HUB): docker hub, nexus, artifactory (all exhibit same behavior)
• OS (e.g. from /etc/os-release): RHEL 7.9

---

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 working on this issue.

[praveenrewar]

My understanding is that it's an issue with the underlying libraries that imgpkg uses (@joaopapereira should be able to confirm once he is back)