Prisma Cloud Compute: Agentless scanning of sub directories

We are scanning the root directory but /root/.nvm partition causes the scan to fail

DEBU 2022-05-30T18:18:20.664 cmd_scan_agentless.go:96 Devices: [/dev/nvme1n1 /dev/nvme1n1p1 /dev/nvme1n1p128 /dev/nvme2n1 /dev/nvme2n1p1 /dev/nvme2n1p128 /dev/nvme3n1 /dev/nvme3n1p1 /dev/nvme3n1p128 /dev/nvme4n1 /dev/nvme4n1p1 /dev/nvme4n1p128]

Scan will be failing with the device status as "busy"

ERRO 2022-05-30T18:18:31.241 cmd_scan_agentless.go:136 Failed to scan /dev/nvme4n1: /dev/nvme4n1 device is busy for too long
ERRO 2022-05-30T18:18:31.247 cmd_scan_agentless.go:136 Failed to scan /dev/nvme2n1: /dev/nvme2n1 device is busy for too long
ERRO 2022-05-30T18:18:31.349 cmd_scan_agentless.go:136 Failed to scan /dev/nvme1n1: /dev/nvme1n1 device is busy for too long

• Prisma Cloud Compute SaaS
• Prisma Cloud Compute Self Hosted version 22.01 and later

This is by design, as Prisma Cloud Compute does scanning only at root volume. 

1. Currently, agentless scans only root volumes which usually contain the OS filesystem.
2. If the machine data is split across multiple volumes, only the root one is scanned. 
3. If the feature is important please open a feature request here.