Do I need to install it somehow? What would be the best practise of doing so? I read somewhere the layering packages using rpm-ostree is not encouraged. So far I have been installing some binaries in /opt/, like kubelet, kubeadm, crictl, CNI plugins by including them as remote files in my ignition config, because the official kubernetes documentation includes steps to copy these binaries on container linux (Installing kubeadm | Kubernetes).
[root@localhost ~]# ls /usr/libexec/crio/
conmon
[root@localhost ~]# systemctl enable crio
Failed to enable unit: Unit file crio.service does not exist.
[root@localhost ~]# whereis crio
crio: /usr/libexec/crio
[root@localhost ~]# ls -ld /usr/libexec/crio
drwxr-xr-x. 2 root root 20 Jan 1 1970 /usr/libexec/crio
[root@localhost ~]# which crictl
/usr/bin/which: no crictl in (/root/.local/bin:/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
[root@localhost ~]# find / -name crio
find: File system loop detected; ‘/sysroot/ostree/deploy/fedora-coreos/deploy/f480038412cba26ab010d2cd5a09ddec736204a6e9faa8370edaa943cf33c932.0’ is part of the same file system loop as ‘/’.
/usr/libexec/crio
[root@localhost ~]# find / -name cri-o
find: File system loop detected; ‘/sysroot/ostree/deploy/fedora-coreos/deploy/f480038412cba26ab010d2cd5a09ddec736204a6e9faa8370edaa943cf33c932.0’ is part of the same file system loop as ‘/’.
[root@localhost ~]#
crictl and cri-o dose not installed in fedora-coreos-31.20200113.3.1
it’s normal, or bug?
You canrpm-ostree install cri-o but that might not be what you want. However you install kubernetes you’ll want your cri-o installation to come from those instructions and be lifecycled with kubernetes itself. We don’t have well defined/published directions for this right now.
Even package layering it is a bit convoluted right now because it’s delivered via a module and not in the default package set in the mirrors. In order to layer it you need to create a file to enable the cri-o stream and also enable the modular repos: