cri-o: Wrong PATH for conmon with the cri-o-1.18.1-1.1.el8 package
Description
After installing the cri-o-1.18.1-1.1 the /etc/crio/crio.conf
expetecs the conmon binary to be located at /usr/libexec/crio/conmon
instead of the /usr/bin/conmon
.
Steps to reproduce the issue:
wget https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.18/CentOS_8/devel:kubic:libcontainers:stable:cri-o:1.18.repo -P /etc/yum.repos.d
dnf install cri-o
systemctl start crio.service
To fix:
sed 's|/usr/libexec/crio/conmon|/usr/bin/conmon|' -i /etc/crio/crio.conf
systemctl start crio.service
Describe the results you received:
– Unit crio.service has begun starting up. May 17 23:07:00 localhost crio[1967]: time=“2020-05-17 23:07:00.078367817-03:00” level=info msg=“Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL” May 17 23:07:00 localhost crio[1967]: time=“2020-05-17 23:07:00.079441070-03:00” level=fatal msg=“Validating runtime config: conmon validation: invalid conmon path: stat /usr/libexec/crio/conmon: no such file or directory” May 17 23:07:00 localhost systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE May 17 23:07:00 localhost systemd[1]: crio.service: Failed with result ‘exit-code’. May 17 23:07:00 localhost systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).
Describe the results you expected:
May 17 23:18:04 localhost systemd[1]: Started Container Runtime Interface for OCI (CRI-O).
Output of crio --version
:
crio version
Version: 1.18.1
GitCommit: 5cbf694c34f8d1af19eb873e39057663a4830635
GitTreeState: clean
BuildDate: 2020-05-16T21:44:39Z
GoVersion: go1.13.4
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
Centos 8 Version:
$ cat /etc/redhat-release
CentOS Linux release 8.1.1911 (Core)
Additional environment details (AWS, VirtualBox, physical, etc.):
VirtualBox
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (10 by maintainers)
I guess we should update the crio docs to disable container-tools module for centos8 and 8stream. Users can get the deps from the main OBS repo which has conmon/skopeo etc. and container-selinux from a copr repo. So, something like:
…followed by the regular instructions to add the crio OBS repo and install crio package. Let me know if that works.
@lsm5 @dougsland with the copr enabled and the container-tools disabled, everything looks good