Running Docker Component Locally Which Relies on GreenGrass Core IPC Client #537
-
We have a NodeJS component which runs fine on a GreenGrass core (Raspberry Pi) as a Docker container. The component uses the Currently when we start the component locally, the What would be the recommended setup for local dev of a component like this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Update: I've been pointed at https://youtu.be/adx3zUGRoWw?t=303&si=CcOgHoGp7qvwdwUp as a possible solution to your question. My original reply (which is a little incomplete on information): If you want to run a component (or any application that uses GG IPC for that matter) without it being managed by a core you'll need to setup some specific environment variables (this is how I run GG IPC directly from an IDE for that matter, I don't actually manage components): https://github.com/aws/aws-iot-device-sdk-js-v2/blob/main/lib/greengrasscoreipc.ts#L23-L24
More information on these can be found here: https://docs.aws.amazon.com/greengrass/v2/developerguide/component-environment-variables.html TLDR: Make a trivial component that logs |
Beta Was this translation helpful? Give feedback.
Update: I've been pointed at https://youtu.be/adx3zUGRoWw?t=303&si=CcOgHoGp7qvwdwUp as a possible solution to your question.
My original reply (which is a little incomplete on information):
If you want to run a component (or any application that uses GG IPC for that matter) without it being managed by a core you'll need to setup some specific environment variables (this is how I run GG IPC directly from an IDE for that matter, I don't actually manage components):
https://github.com/aws/aws-iot-device-sdk-js-v2/blob/main/lib/greengrasscoreipc.ts#L23-L24