Component not stopped on new deployment

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 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 ?

주제

사물 인터넷(IoT)컨테이너

태그

AWS IoT Greengrass 아마존 엘라스틱 컨테이너 서비스 컨테이너

언어

English

TSpark

질문됨 2년 전239회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

수락된 답변

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.

전문가

MichaelDombrowski-AWS

답변함 2년 전

TSpark
2년 전
Awesome that is what I was looking for. Thanks ! Additionally, is there a way to see the status of containers on the devices through AWS ? Something similar to portainer or docker ps ?
MichaelDombrowski-AWS 전문가
2년 전
No, there isn't any way provided by Greengrass to show your containers. Only the component status is reported to the cloud.

Component not stopped on new deployment

관련 콘텐츠