You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with kbld relocate it seems to get the right digest but there is another error related to that hash (451a3e5dc6813d40a15af2e2e45d24e80782db54a8e7c3e9858c711e094da6b3) that I cannot find anywhere in the manifests :
What did you expect:
The proper image is copied on the target registry without issue.
Anything else you would like to add:
The copy from quay.iois working with skopeo without issue.
There is also no issue in relocating images from Docker HUB with the same imgpkg copy command.
Environment:
imgpkg version (use imgpkg --version): 0.14.0
Docker registry used (e.g. Docker HUB): quay.io
OS (e.g. from /etc/os-release): Ubuntu 20.04.2
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.
The text was updated successfully, but these errors were encountered:
There is a known issue around copying an image index which quay.io/bitnami/sealed-secrets-controller@sha256:cb183c914323dcad01a46e6c879368b2f4706a2c021a9386fb6a6a5e8768fa37 is
What steps did you take:
I'm trying to relocate with imgpkg copy an image from quay.io registry to an internal private registry.
What happened:
imgpkg copy --lock sealed-secrets-v0.16.0.lock --to-repo private-registry/sealed-secrets-controller
with sealed-secrets-v0.16.0.lock being :
resulted in exporting a wrong digest:
When exporting to tar, no error is thrown but the digest is still wrong :
with kbld relocate it seems to get the right digest but there is another error related to that hash (451a3e5dc6813d40a15af2e2e45d24e80782db54a8e7c3e9858c711e094da6b3) that I cannot find anywhere in the manifests :
What did you expect:
The proper image is copied on the target registry without issue.
Anything else you would like to add:
The copy from quay.iois working with skopeo without issue.
There is also no issue in relocating images from Docker HUB with the same imgpkg copy command.
Environment:
imgpkg --version
): 0.14.0Docker HUB
): quay.io/etc/os-release
): Ubuntu 20.04.2Vote 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.
The text was updated successfully, but these errors were encountered: