This message was deleted.
# harvester
a
This message was deleted.
b
There is no container involved in the way you're thinking. It may be easier to think of it this way: the cluster is treating libvirt (running on each node) as if it were replacing the docker daemon (it's not, but think of it that way).
Or said differently, kubevirt is acting as a cri (what is really happening). It's just that the ‘container’ happens to be a full vm and the runtime happens to be libvirt.
🙌 1
b
ah thank you. that clears things up. i'll have to look into it more. i've been listening to Devops and Docker off/on, but i'm just now getting back into development, so everything is new again.