walters added a new comment to an issue you are following:
One bifurcation I see here is that larger scale systems do want decoupled host upgrades
("I want to yum update/rpm-ostree upgrade without upgrading
But for smaller scale systems ("I have a home server") decoupling the container
runtime feels like a lot of overhead. But eh, we can probably fix that.
I think my vote here is to focus on system containers for Kube/OpenShift first... which
actually doesn't answer the question.
If we're going to default to containerized cri-o, I think we need to fix things
upstream. Right now the upstream docs follow the (IMO anti-pattern) of installing build
dependencies on a *host* and doing a `sudo make install`.
With the latest FAH `rpm-ostree install cri-o` seems to work fine FWIW.
To reply, visit the link below or just reply to this email