Comment # 1 on bug 1104598 from Valentin Rothberg

(In reply to Richard Brown from comment #0)
> /etc/crictl.yaml is consumed by the crictl binary provided by cri-tools
> 
> But /etc/crictl.yml is currently packaged as part of cri-o
> 
> This seems very wrong to me

I understand that it seems weird, but that's just how upstream provides those
files. However, I agree that we should move the config to cri-tools.

> And also has very real world issues - as crictl on Kubic is constantly
> complaining about the deprecated syntax for it's container runtime endpoint,
> which should be unix:///var/run/crio/crio.sock not the current
> /var/run/crio/crio.sock
> 
> 2 Solutions are possible
> 
> Option a) get crictl.yaml packaged in cri-tools instead
> or 
> b) get cri-o packaged in devel:kubic and caught up with the respective
> cri-tools version to solve this discrepency
> 
> Valentin, which do you prefer?

A mix of both :^)  The `crictl.yaml` should go into cri-tools (with the "unix:"
scheme fix) and cri-o should be moved to devel:kubic.

Notice, that I already have a cri-o 1.11.x package but didn't submit it yet as
there is a build regression regarding apparmor. I already have a PR open but
the upstream e2e flakiness blocks the merge. I will downstream-patch the
package for now, so that we can proceed.

Thanks a lot for opening the bug!