I am trying to create a Kubernetes cluster using cri-o as the container runtime but have been unable to get cri-o installed through the module repos. This has worked for me before, so I am not sure what I may be missing to get it installed.
I’ve created a file named cri-o.module in the /etc/dnf/modules.d directory with the following:
I have tried different versions of cri-o (1.19, 1.18 etc.) but get always get the same error. I do see the package in the modular repo, but for some reason rpm-ostree does not. I’m fairly new to FCOS and to rpm-ostree in general, but as I mentioned, this has worked for me in the past.
Can either of you help me understand the concept of enabling versus just layering? Specifically, @walters you have me enable and then install via the typical rpm-ostree where @dustymabe method just adds the layer for cri-o which is similar to what I did prior to the changes.
Also, I’m curious as to where I can read to better understand the desired end state to how you will handle modules? I’m guessing nothing is formally documented and I’ll need to troll the PRs?
I think of enabling like adding a repo to which you can pull packages from and the install being the actual pull+layer. The command I provided does both the enablement and the layering as a convenience IIUC.
Yeah I’m not sure our documentation has been updated for module support.