From Fedora Project Wiki

Enable bootupd for Fedora Atomic Desktops and Fedora IoT


By design, ostree does not manage bootloader updates as they can not (yet) happen in a safe fashion. To solve this issue, bootupd ( was created. bootupd is a small socket activated program that takes care of updating the bootloader. It currently only supports EFI booted systems and rpm-ostree based systems. The updates are triggered by an administrator and are not (yet) automated for safety reasons. This change is about enabling bootupd integration in Fedora Atomic Desktops and Fedora IoT to make bootloader updates easier. bootupd is already used in Fedora CoreOS.


Current status

Detailed Description

Adding full bootupd support has two immediate benefits:

Note that we can not yet enable unattended bootloader updates as even though bootupd tries hard to make those updates as safe as possible, it is currently not possible that they are safe if the system crashes (or loses power) at the wrong time. The following change in shim ( should help with that.

Thus bootloaders updates will remain a manually user triggered operation for now.

Also note that this change currently relies on the image being composed via rpm-ostree in unified core, which is the subject of the following change also proposed for Fedora 38:


> What's the plan to apply the outstanding security updates (shim, grub2, and dbx push from June) to fedora silverblue 36 + 37 that aren't covered by this change?

We'll try to backport as much as possible of this change to Fedora 37 and Fedora 36 to let users updates their bootloaders. If we require Anaconda changes (unlikely but not 100% sure at the time this is written) then those changes will not be backported as we don't respin the installer ISOs.

Benefit to Fedora

Fedora Atomic Desktops and Fedora IoT users can easily do bootloaders updates (that includes security fixes) and we can remove support for legacy GRUB versions thus simplify the upgrade process and making it more reliable.


  • Proposal owners: Testing of the integration and new builds. The code changes are mostly done and the integration changes are mostly already ready as bootupd has already been integrated in a similar fashion in Fedora CoreOS.
  • Other developers: N/A
  • Release engineering: N/A
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives: N/A

Upgrade/compatibility impact

There should be not visible change for users when upgrading. The change only impacts the way the images are composed on the server.

How To Test

We will extend the test instructions once the unified core changes have landed. You can follow: and

User Experience

For now, users will have to update their bootloader manually via the command line. Integration to GNOME Software and Plasma Discover might be interesting to make that easier.

Once the fallback EFI feature is available in shim (and support implemented in bootupd), we can consider implementing automated updates.



Contingency Plan

  • Contingency mechanism: Revert the change in the rpm-ostree manifests. Owners will do it. Nothing to do for users.
  • Contingency deadline: Can happen anytime.
  • Blocks release? No


We will write docs to let users update their bootloaders manually. They will look very similar to

Release Notes

Will have to be written.