notary-server failed to start due to ssl certificate issue

goharbor / harbor-arm

Build Harbor for arm architecture.

Apache License 2.0

73 stars 45 forks source link

notary-server failed to start due to ssl certificate issue #16

Closed Jeremy-boo closed 3 years ago

Jeremy-boo commented 3 years ago

// notary-server error info {"level":"fatal","msg":"unable to set up TLS: Error reading X509 key pair (cert: \"/etc/notary/notary-signer.crt\", key: \"/etc/notary/notary-signer.key\"): tls: failed to find any PEM data in certificate input. Make sure the key is not encrypted.","time":"2021-11-12T02:32:44Z"}

wy65701436 commented 3 years ago

from the log, it seems that the binary in the notary-server is for the notary-signer, please confirm it. @Jeremy-boo

Jeremy-boo commented 3 years ago

Because docker buildx has a cache, the basic image of notary-signer is used when constructing notary-server. Before constructing notary-server, execute the docker buildx prune -f command to solve this problem

Jeremy-boo commented 3 years ago

done