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
I have write a container image distribution client which will fill urls into manifest.
When i push some image via my distribution client to my self-signed image registry, containerd can not pull the image down.
And the stdout is following:
As we can see, ctr report an error x509 when httpReadSeeker is failed to open a remote blob file from external url.
And finally, I found that the code should be blame by https://github.com/containerd/containerd/blob/main/core/remotes/docker/fetcher.go#L73, where the host is not provided by https://github.com/containerd/containerd/blob/main/core/remotes/docker/config/hosts.go#L74.
Steps to reproduce the issue
Put an image manifest with external urls which pointed to a self-signed cert host
pull image via containerd
Describe the results you received and expected
External urls fetcher should follow registry tls verify skip configuration.
Description
I have write a container image distribution client which will fill urls into manifest.
When i push some image via my distribution client to my self-signed image registry, containerd can not pull the image down.
And the stdout is following:
As we can see,
ctr
report an errorx509
whenhttpReadSeeker
is failed to open a remote blob file from external url.And finally, I found that the code should be blame by
https://github.com/containerd/containerd/blob/main/core/remotes/docker/fetcher.go#L73
, where thehost
is not provided byhttps://github.com/containerd/containerd/blob/main/core/remotes/docker/config/hosts.go#L74
.Steps to reproduce the issue
Describe the results you received and expected
External urls fetcher should follow registry tls verify skip configuration.
What version of containerd are you using?
containerd github.com/containerd/containerd v1.7.1 1677a17
Any other relevant information
The Image Manifest look like:
Show configuration if it is related to CRI plugin.
The text was updated successfully, but these errors were encountered: