Prisma cloud compute is not scanning harbor registry images after configuration

Ganesh — Thu, 27 Apr 2023 13:38:56 GMT

Failed to pull image test/share-app:1.0.377, error error initializing source docker://harbor-d.xyz.com/test/share-app:1.0377:error pinging docker registry harbor-d.xyz.com: Get "https://harbor-d.xyz.com/v2/"x509: certificate signed by uninown authority

Hi I am actually configured prisma cloud compute with harbor registry.

Defenders are there when I've clicked on scan it is scanning the images but I went to see results Monitor> Vulnerabilities > Images > Registries

I can see the above error. If anyone knows the solution please let me know.

Thanks,

Ganesh.

Re: Prisma cloud compute is not scanning harbor registry images after configuration

NPerez — Tue, 05 Sep 2023 17:45:40 GMT

Hi,

I am looking old questions to answer and I apologize that this question went unanswered.

The error "x509: certificate signed by unknown authority" sounds like an issue with pulling the image in general. Assuming you are using docker. I recommend attempting to pull the image manually ($ docker pull). The defender will interact with the underlying docker daemon to pull the image but ultimately the docker daemon is going to pull the image.

I've seen similar errors with $docker pull if you try to connect to an insecure registry. I've had to configure the docker daemon to permit connecting to insecure registries before $docker pull would work.

https://docs.docker.com/registry/insecure/

If you are able to pull manually, then the defender should be able to pull the image as well. If not, collect defender and console logs for review. They are located in the /var/lib/twistlock/log directory

topic Prisma cloud compute is not scanning harbor registry images after configuration in Prisma Cloud Discussions

Prisma cloud compute is not scanning harbor registry images after configuration

Re: Prisma cloud compute is not scanning harbor registry images after configuration