- Newest
- Most votes
- Most comments
Hello,
Greengrass Lambdas use container technology for process isolation and reduced security concerns. I highly suspect that you won't be able to run this command from within the container and have it work. You can switch your lambda to run without a container such that it is just running a process directly on the hardware in the same way that you would run a process on the commandline.
When changing from container to non-container you will create a new Greengrass component from the lambda and select non-container mode. When deploying this updated Greengrass component version to the device you must edit the configuration update options in order to set the configuration on the device to use the new values. Specify "RESET": [""]
to reset all configuration for the component to the new values. Learn more about reseting configuration here: https://docs.aws.amazon.com/greengrass/v2/developerguide/update-component-configurations.html#reset-configuration-update
Thanks Michael,
Problem solved with non-container and "RESET": [""]
parameter.
Thanks a lot.
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago