Closed maggie44 closed 3 years ago
When Balena Supervisor restarts (updates, device reboot etc.), it ignores monitored container restart policies and restarts the containers. This is an issue for things like Portainer which allows the user to shut down the service.
A manual fix has been applied which is effective and sufficient: https://github.com/LearnersBlock/learners-block/pull/172
Ideally though, the Supervisor would follow standard Docker practice and observe the restart polices. There is a ticket open for this with Balena (https://github.com/balena-os/balena-supervisor/issues/1668), and when resolved can remove the fix applied (https://github.com/LearnersBlock/learners-block/pull/172).
Leaving here for reference.
When Balena Supervisor restarts (updates, device reboot etc.), it ignores monitored container restart policies and restarts the containers. This is an issue for things like Portainer which allows the user to shut down the service.
A manual fix has been applied which is effective and sufficient: https://github.com/LearnersBlock/learners-block/pull/172
Ideally though, the Supervisor would follow standard Docker practice and observe the restart polices. There is a ticket open for this with Balena (https://github.com/balena-os/balena-supervisor/issues/1668), and when resolved can remove the fix applied (https://github.com/LearnersBlock/learners-block/pull/172).
Leaving here for reference.