From Fedora Project Wiki

No edit summary
No edit summary
Line 10: Line 10:


  rpm-ostree rebase fedora-{{FedoraVersionNumber|current}}:fedora-atomic/f{{FedoraVersionNumber|current}}/x86_64/docker-host
  rpm-ostree rebase fedora-{{FedoraVersionNumber|current}}:fedora-atomic/f{{FedoraVersionNumber|current}}/x86_64/docker-host
Like any other rpm-ostree update, this is staged for the next reboot, so to finally apply the update:
systemctl reboot


That should be all!
That should be all!

Revision as of 11:01, 22 June 2016

Fedora Atomic Host installations use the rpm-ostree deployment method, where packages are assembled on the Fedora release engineering side and delivered as atomic units, rather than the yum/DNF method of client side assembly. Consequently, they do not use the DNF system upgrade mechanism which is used to upgrade between Fedora releases for other Fedora installations. Instead, use the procedure described here.

Note.png
One OSTree repository per release
It's crucial to note that at the moment, Fedora uses separate OSTree repositories for each major release. This makes switching between versions more painful. For more information, see this ticket.

Let's assume you're upgrading from Fedora 39 to 40. First, you'll need to add a remote for the new major version:

ostree remote add fedora-40 --set=gpg-verify=false https://dl.fedoraproject.org/pub/fedora/linux/atomic/40

Then, rebase to it:

rpm-ostree rebase fedora-40:fedora-atomic/f40/x86_64/docker-host

Like any other rpm-ostree update, this is staged for the next reboot, so to finally apply the update:

systemctl reboot

That should be all!