From Fedora Project Wiki

No edit summary
No edit summary
Line 1: Line 1:
Fedora Atomic Host installations use the [https://rpm-ostree.readthedocs.org/en/latest/ 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.
This article applies to Fedora Atomic Host (though there is also an experimental [https://pagure.io/workstation-ostree-config/ workstation-ostree]).  For Fedora Workstation and Server, see [[DNF system upgrade]].
 
Fedora Atomic Host installations use the [https://rpm-ostree.readthedocs.org/en/latest/ rpm-ostree deployment method], where the same packages used in Workstation/Server are assembled on the Fedora release engineering side and delivered as versioned atomic units, rather than the traditional yum/DNF method of client side assembly.   


{{admon/note|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 [https://fedorahosted.org/rel-eng/ticket/6125 this ticket].}}
{{admon/note|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 [https://fedorahosted.org/rel-eng/ticket/6125 this ticket].}}

Revision as of 21:50, 11 July 2017

This article applies to Fedora Atomic Host (though there is also an experimental workstation-ostree). For Fedora Workstation and Server, see DNF system upgrade.

Fedora Atomic Host installations use the rpm-ostree deployment method, where the same packages used in Workstation/Server are assembled on the Fedora release engineering side and delivered as versioned atomic units, rather than the traditional yum/DNF method of client side assembly.

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.

Upgrading from Fedora 25 Atomic Host to Fedora 26 Atomic Host:

First, be sure you have enough storage in the root partition:

lvm lvextend atomicos/root -L +2G -r

Next add the remote, then rebase:

ostree remote add --if-not-exists --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-primary fedora-atomic-26 https://kojipkgs.fedoraproject.org/atomic/26
rpm-ostree rebase fedora-atomic-26:fedora/26/x86_64/atomic-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!