-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
CentOS Stream 10
-
None
-
Yes
-
Critical
-
rhel-container-tools
-
3
-
None
-
None
-
None
-
None
-
Unspecified
-
None
What were you trying to do that didn't work?
RPMS="gcc git-core iptables jq glibc-static libseccomp-devel make criu fuse-sshfs container-selinux"
{{{}dnf install -y --setopt=install_weak_deps=False --setopt=tsflags=nodocs $RPMS
{}}}results in %post script warnings (not failure!)
> ...
> Running scriptlet: container-selinux-4:2.246.0-1.el10.noarch 26/37
> Installing : container-selinux-4:2.246.0-1.el10.noarch 26/37
> Running scriptlet: container-selinux-4:2.246.0-1.el10.noarch 26/37
> libsemanage.semanage_pipe_data: Child process /usr/libexec/selinux/hll/pp failed with code: 255. (No data available).
> libsemanage.semanage_compile_module: container: libsepol.policydb_read: policydb module version 24 does not match my version range 4-23.
> libsemanage.semanage_compile_module: container: libsepol.sepol_module_package_read: invalid module in module package (at section 0).
> libsemanage.semanage_compile_module: container: libsepol.sepol_ppfile_to_module_package: Failed to read policy package.
> libsemanage.semanage_direct_commit: Failed to compile hll files into cil files. (No data available).
> semodule: Failed!
> ...
after which the following command fails:
>- chcon:- failed- to- change- context- of- '/tmp/bats-run-3MMyYP/runc.szTqBc/bundle/runc'- to- 'system_u:object_r:container_runtime_exec_t:s0':- Invalid- argument↲
(all this is from upstream runc CI, see e.g. https://cirrus-ci.com/task/6663486962401280)
What is the impact of this issue to you?
runc CI is broken (being fixed by https://github.com/opencontainers/runc/pull/5123).
Please provide the package NVR for which the bug is seen:
4:2.246.0-1.el10
How reproducible is this bug?:
Always
Steps to reproduce
- Have a CentOS Stream 10 system with policycoreutils-3.9-3.el10 installed and container-selinux not installed.
- Run `dnf install container-selinux`
Expected results
No warnings from `dnf install`, after installation chcon command from the above description works fine.
Actual results
See above