Does resin.io always assume that every container needs to continuously keep running?
I’ve built a simple Dynamic DNS application which consists of two containers. One configures the Dynamic DNS service settings (based on environment variables) and then exists immediately (edit: added for clarity). Another one checks the device’s IP address every 5 minutes and performs an update if necessary.
Currently, I need to insert a dummy wait statement, so that resin.io does not try to continuously restart the first one (I assume this operation is not very power efficient, especially given that it’s unnecessary):
Is there a way to make resin.io be okay with a short-lived container? Or is there a better solution to my problem? Ideally I’d like to keep the container separation between the configuration and IP update.
(On a related note, I suppose it would be more efficient to fire up the IP update container every 5 minutes. Now it takes up RAM on just waiting for another check. This may or may not matter, depending on whether you can run other containers only when this one is down.)
In any case, resin.io is absolutely amazing – creating this project was a pleasure! Thanks for making it happen!