- Newest
- Most votes
- Most comments
Hi,
Please make sure you follow the instructions for containerized lambda here https://docs.aws.amazon.com/greengrass/v1/developerguide/ml-dlc-console.html#ml-console-dlc-config-lambda. Specifically choose Use group default for Run as instead of using 0 for UID/GUID.
Also make sure you're adding both /dev/vcsm and /dev/vchiq as resources to the GG group with correct file access permissions and Lambda function affiliations, as documented here https://docs.aws.amazon.com/greengrass/v1/developerguide/ml-dlc-console.html#ml-console-dlc-add-cam-resource.
Thanks,
Anmol
Anmol,
Thank you again. The problem was solved! I thought running Lambda as root clears all the permission problems.
I ran Lambda as group default(ggc_user), after adding /dev/vcsm and /dev/vchiq resource to the GGG, and it worked.
It took a while for me to understand adding volume and device resource to GGG is purely for the sake of container, while adding ML model resource to GGG is not.
Thanks:)
HM