No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
Next add the remote, then rebase: | Next add the remote, then rebase: | ||
ostree remote add --if-not-exists -- | 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 | rpm-ostree rebase fedora-atomic-26:fedora/26/x86_64/atomic-host | ||
Revision as of 18:49, 11 July 2017
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.
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!