You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BTW on socket path, I had issues with "unix:///" prefix (Err: connection error: desc = "transport: error while dialing: dial unix unix:///var/run/crio/crio.sock: connect: no such file or directory")
what worked was a direct path "/var/run/crio/crio.sock" for both --runtime-socket & --image-socket in EnvironmentFile=/etc/sysconfig/cri-resource-manager
OpenShift version 4.10.11
Kubernetes version v1.23.5+9ce5071
OS-IMAGE Red Hat Enterprise Linux CoreOS 410.84.202204112301-0 (Ootpa)
KERNEL-VERSION 4.18.0-305.40.2.el8_4.x86_64
CONTAINER-RUNTIME cri-o://1.23.2-6.rhaos4.10.git9a36bb8.el8
The text was updated successfully, but these errors were encountered:
Describe the bug
According to https://intel.github.io/cri-resource-manager/stable/docs/setup.html#setting-up-cri-resource-manager
setting --image-socket is optional, while from my experience for cri-o it is mandatory
and one needs both --image-socket and --runtime-socket to point to cri-o socket
BTW on socket path, I had issues with "unix:///" prefix (Err: connection error: desc = "transport: error while dialing: dial unix unix:///var/run/crio/crio.sock: connect: no such file or directory")
what worked was a direct path "/var/run/crio/crio.sock" for both --runtime-socket & --image-socket in EnvironmentFile=/etc/sysconfig/cri-resource-manager
Expected behavior
Please update https://github.com/intel/cri-resource-manager/blob/master/docs/setup.md
so that one can follow it without facing issues for crio runtime
To Reproduce
Follow https://intel.github.io/cri-resource-manager/stable/docs/setup.html for cri-o as-is
Environment
OpenShift version 4.10.11
Kubernetes version v1.23.5+9ce5071
OS-IMAGE Red Hat Enterprise Linux CoreOS 410.84.202204112301-0 (Ootpa)
KERNEL-VERSION 4.18.0-305.40.2.el8_4.x86_64
CONTAINER-RUNTIME cri-o://1.23.2-6.rhaos4.10.git9a36bb8.el8
The text was updated successfully, but these errors were encountered: