Stop
Stops the gateway container. The state remains intact — systemd registration, image,
/data1, and /etc/kopens are not touched.
sudo /opt/kopens/plantpulse-edge-docker/bin/stop.sh
To bring it back up, use start.sh or
systemctl start plantpulse-edge.service.
Stopping is different from removing
stop.sh only stops the container. To remove the installation itself, use undeploy.sh;
in that case, the systemd registration and the container disappear together. The data disk
is managed under a separate policy.
What happens during a stop
When the container goes down, collection also stops. The edge's local queue is not inside
the container — it resides in /data1, so nothing accumulates during the stop, but data
queued before the stop is preserved. Data that was being sent to the platform will resume
once it comes back up.
Verification
cd /opt/kopens/plantpulse-edge-docker/bin
./status.sh # 내려갔는지
docker ps -a --filter name=plantpulse-edge # 컨테이너 상태