Package systems are also quite fragile, ie if a post-trigger/script fails the package install fails. And sometimes not cleanly either, where the partially-installed package blocks install of a new fixed package. In the worst case the system is left in an in-between broken state.
I also am trying to get Resin.io like containers working. It seems like it would be an easier way to test and deploy.
We fiddled around also a little bit with the container route. I liked it for quick iteration times (rebuild a docker container, pull it from local image registry to device and test it there). But we found out that we won't get by with just container updates, and that most updates would also need to contain a new kernel or kernel module versions.
Like you, many teams are still doing local updates, or transitioning from local to OTA, at least for some products.
[0] https://docs.mender.io/1.0/Architecture/Overview#modes-of-op...
- Build system: Would need to figure out how to build all these packets (with their requirements) in a reliable way.
- Deployment: Deployments should be reproducable. All devices should get the same version of all subcomponents. And a rollback to an older version (with older versions of subcomponents) should be possible. Having some devices floating around with untested configurations (because the device decided to update on package but not the remaining ones) is not desirable, because you want to only handover fully tested/qualified software versions to the customer.
Building the whole RFS at once, storing it and flashing it at once currently seems like the way to go. Will take a look at mender if it could help.