smilner added a new comment to an issue you are following:
I think one way of doing this is to copy the CRI-O clients (crioctl,
kpod, something else?) to the host so that they can be accessed directly without requiring
I am very biased on this topic but I don't see the point of adding another component
to the host image when it works very well from a container. Also, if the need arises we
have package layering.
I'm with you on that. The worry is around it being as easy to access as docker since
docker is going to remain in the base (though folks who need a different version for
OpenShift or other things will continue to use system containers). We don't want to
discourage the use of docker at all, but we also don't want to discourage the use of
cri-o because you have to jump through hoops.
To reply, visit the link below or just reply to this email