-
Notifications
You must be signed in to change notification settings - Fork 98
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
It failed to pull gcr.io/k8s-staging-cloud-provider-ibm/ibm-vpc-block-csi-driver:master by image-rs #76
Comments
Hi @liudalibj , thanks a lot for reporting this bug and providing reproducing steps! This issue may be related to confidential-containers/enclave-cc#60 as well. As I tested, the test image you've given The logic inside Thus for those images who have duplicated layers will all show this error. I think there should add some code to filter duplicated |
When an image to be pulled has duplicated layers, the 2nd layer will write the same layer data and raise layer. This is because the time to update the database that stores layer metadata is after pulling all layers of an image. This commit will try to construct a new layer list to be pulled via deduplicating the layers of the OciManifest. Close #76 Signed-off-by: Xynnn007 <[email protected]>
Fix: confidential-containers#76 Signed-off-by: Jiale Zhang <[email protected]>
It failed to pull gcr.io/k8s-staging-cloud-provider-ibm/ibm-vpc-block-csi-driver:master by image-rs
When I followed the document to run peer-pod nginx demo succeed. (I run the demo on x86 arch, and the kata-agent using image-rs(0.2.0) to pull/unpack docker images).
But when I try to replace the docker image from
nginx
to others(eg. gcr.io/k8s-staging-cloud-provider-ibm/ibm-vpc-block-csi-driver:master) I got a failed result, from thecloud-api-adaptor
log it said something like this.Login to the podVM and check related agent-protocol-forwarder/kata-agent log:
This issue can be reproduced simply, after we got image-rs codes:
Add the test images to vet at here:
https://github.com/confidential-containers/image-rs/blob/main/src/image.rs#L351
And then run
in the console it will show something like:
Here is the Dockerfile for
gcr.io/k8s-staging-cloud-provider-ibm/ibm-vpc-block-csi-driver:master
The text was updated successfully, but these errors were encountered: