On Thu, Jan 05, 2017 at 05:09:59PM +0000, Daniel P. Berrange wrote: > More work for the end user to keep their systems updated. Containers in > general are a retrograde step in this area, since instead of being able > todo a simple "dnf update" on the host and have everything updated, you > have to do "dnf update" and then figure out how to update each individual > container. Even if we assume the 32-bit container base image lets you use > dnf normally, this change has at least added an extra step for users > as they have to upgrade their 64-bit and 32-bit container via separate > "dnf update" command invokations. > > Regards, > Daniel I think we're only considering this for the modular composes, where containers would be just instance of modules, managed by the base system, presumably through something as simple as "dnf update". Plenty of assumptions but I believe that's the plan. P
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
