This seems likely a duplicate of balena thinks service is downloaded but it will not start
I have noticed several times that Balena will only partially update a device to a new release–some containers will get ‘stuck’, displaying ‘Downloaded → Running’ in the dashboard but never actually switching to the newer release. Like the other forum post, restarting/rebooting has sometimes fixed this, but as of today I am faced with a container that will not update even after rebooting the device.
We (well I at least) would really like to green-light Balena for our project, but this issue is serious enough to affect our decision.
Is there at least some sort of workaround more elegant than ‘push another release and hope that one works’?