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
When using ctr image import --local=false to depend on the newer transfer service which uses the unpacker under the hood, it successfully transfers the image into the content store but it is missing a client.ImageService().Create(...) call. I assume this is the client's responsibility and not pkg/transfer/local/import.go?
Without this step, kubernetes won't be able to discover the image even though it is visible with ctr image ls or nerdctl image ls.
Steps to reproduce the issue
ctr image import --local=false ./oci.tar
Run image via CRI interface, e.g. crictl or kubernetes.
Description
When using
ctr image import --local=false
to depend on the newertransfer
service which uses the unpacker under the hood, it successfully transfers the image into the content store but it is missing aclient.ImageService().Create(...)
call. I assume this is the client's responsibility and notpkg/transfer/local/import.go
?Without this step, kubernetes won't be able to discover the image even though it is visible with
ctr image ls
ornerdctl image ls
.Steps to reproduce the issue
ctr image import --local=false ./oci.tar
crictl
or kubernetes.failed to resolve image ...
here: https://github.com/containerd/containerd/blob/v1.7.2/pkg/cri/server/container_create.go#L96-L99Describe the results you received and expected
Image imported with
--local=false
to be runnable via CRIWhat version of containerd are you using?
v1.7.2
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response
The text was updated successfully, but these errors were encountered: