Component not stopped on new deployment

Question

I am trying out GreenGrass v2 to see if it would fit our need to deploy our stack using docker-compose to our IoT devices.
I have followed the steps [here](https://docs.aws.amazon.com/greengrass/v2/developerguide/run-docker-container.html) and setup a device with a deployment (i.e. 1.0.1).

I am not exactly clear how components interact with docker-compose, it seems that even when I stop a container manually, it will reset on reboot. That is not a problem, but it also looks like when I publish a new deployment (i.e. 1.0.2), I still have containers from 1.0.1 still running, which ends up throwing errors because they are trying to access the same ressource.

What is the correct approach to stop the docker-compose stack when I deploy a new update ?

Accepted Answer

Hi TSpark,

Thank you for your question. You should utilize the `shutdown` lifecycle step to call `docker-compose down` for example. The shutdown step is called when Greengrass stops or when the component will be updated. Therefore, you should write whatever commands are needed to safely and completely shutdown your component.

Component not stopped on new deployment

Relevanter Inhalt