-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support a boot-once + broken new boot -> rollback model #177
Comments
It'd probably make sense to bake in auto-rollback functionality into rpm-ostreed itself. We don't yet have a Figure out a good way to hook in activating a service if reaching Something like:
in |
See also ostreedev/ostree#380 |
FWIW we actually now do have a config file. |
Note that there is a new project called greenboot that tries to address this: https://github.com/LorbusChris/greenboot. |
See also https://pagure.io/fedora-iot/issue/12. |
Going to close this in favour of coreos/fedora-coreos-tracker#47 since I think in the end this is something that has to be designed at a higher level. |
Some bootloaders have support for "boot once". Combined with a userspace sanity check (say e.g. a
multi-user.target
service fails), trigger an automatic rollback.This would help enable automatic updates; see #44
The text was updated successfully, but these errors were encountered: