MicroOS relies on atomic Linux updates
Summary
Hackaday tests openSUSE MicroOS, whose transactional updates, Btrfs snapshots and separated applications are meant to keep the system in a robust state. MicroOS comes from the openSUSE project. The system is aimed particularly at container hosts and robust devices.
Ideas
- System updates create a new Btrfs snapshot.
- A reboot activates the fully prepared version.
- Failed updates can be rolled back to earlier snapshots.
- Desktop applications are preferably installed as isolated Flatpaks.
Insights
- Immutability shifts administration from individual files to versioned system states.
- Atomic updates prevent half-finished mixed states.
- Rollback does not replace a backup of changing user data.
Facts
- GNOME and KDE were available as desktop variants.
Recommendations
- Test rollback and data persistence before using it in production.
- Visibly separate system state, configuration and user data.
References
Links to the original source and the Web Archive open in a new tab.