For details on cookie usage on our site, read our Privacy Policy
Prisma cloud compute is not scanning harbor registry images after configuration
- LIVEcommunity
- Discussions
- Cloud Native Application Protection
- Prisma Cloud Discussions
- Prisma cloud compute is not scanning harbor registry images after configuration
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Prisma cloud compute is not scanning harbor registry images after configuration
- Mark as New
- Subscribe to RSS Feed
- Permalink
04-26-2023 04:58 AM - edited 04-27-2023 06:38 AM
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.
- Docker image is not detecting in Prisma Cloud Discussions
- images scanning: propagate CI image scan rules to registry scan in Prisma Cloud Discussions
- How can I configure Prisma Compute to Auto-Manage registry scan settings for AWS Accounts lifecycle events? in Prisma Cloud Discussions
- How / where can I find log(s) for Failed Registry Scans? in Prisma Cloud Discussions
Show your appreciation!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
