This message was deleted.

You are indeed correct that images are loaded into memory and that’s also where configuration is stored. I personally can’t comment on the disc activity that you’re seeing because I’ve never bothered to look at it while this is going on. 😄

Based on best practices, the following is recommended: "Large image scanning. The Scanner container must have enough memory to pull the image to be scanned into memory and expand it. If images larger than 1GB are to be scanned, increase memory to the scanner to slightly higher than the largest expected image size." _Source: https://open-docs.neuvector.com/deploying/production/NV_Onboarding_5.0.pdf_ it says nothing about filesystem, could this be a bug?