containerd cannot login harbor registry (x509: certificate relies on legacy Common Name field, use SANs instead
)
#1116
-
Descriptioncontainerd cannot login harbor registry:
However, I can login with docker
Steps to reproduce the issueDescribe the results you received and expectedI expect to login successfully with the correct username and passwork. What version of containerd are you using?containerd github.com/containerd/containerd v1.5.8 1e5ef943eb76627a6d3b6de8cd1ef6537f393a71 Any other relevant informationThe step to generate a Certificate Authority Certificate of my harbor registry : https://goharbor.io/docs/2.5.0/install-config/configure-https/ Show configuration if it is related to CRI plugin.The configs of containerd:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Expected behavior of golang’s x509 lib. |
Beta Was this translation helpful? Give feedback.
-
(I converted this discussion from containerd/containerd#7039 but containerd/containerd#7039 doesn’t seem linked to this discussion 😞 ) |
Beta Was this translation helpful? Give feedback.
-
try to use --insecure-registry +nerdctl login --insecure-registry --username admin --password Harbor12345 https://192.168.9.233:30003/ time="2022-09-07T09:41:12Z" level=warning msg="WARNING! Using --password via the CLI is insecure. Use --password-stdin." Login Succeeded |
Beta Was this translation helpful? Give feedback.
Expected behavior of golang’s x509 lib.
Please set SANs.