On Thu, Feb 11, 2016 at 3:13 PM, Colin Walters <walt...@verbum.org> wrote: > "rpm-ostree container" is a *lot* faster and has the advantage > of understanding when a container needs to be updated.
I saw Colin's demo at DevConf.cz, and I like this architecture the best. It makes the most amount of sense, and knowing when something needs to be updated doesn't happen without inspection with docker. IOW, the "yum update && clean all" layer never knows when to be refreshed with docker! If I had my choice of components, I'd recommend we work on rpm-ostree + nspawn. If we are happy to wait a year, the mgmt piece for describing the layer would be a viable option.
