upgrades in a container


systemd offline updates, used in Fedora and maybe others (?),
downloads all the rpms, reboots the computer into a minimalist
system-update.target, installs the rpms, then reboots again, back to
default.target. The logic of the 1st reboot is to put the system in a
known clean minimal state, so nothing in the current environment is
leaking into the update process.

Question as it relates to rpm-ostree: does it make any sense to have
ostree upgrades done in an nspawn container? Does it improve the
chances of a successful upgrade?

Chris Murphy

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]