Comment # 10 on bug 1230643 from Cathy Hu

okay my guess is that if you delete all these empty directories (check if they
are empty before!) and then run `semodule -l`, it should work again without the
error:

/var/lib/selinux/targeted/active/modules/100/ajaxterm/
/var/lib/selinux/targeted/active/modules/100/authconfig
/var/lib/selinux/targeted/active/modules/100/bumblebee
/var/lib/selinux/targeted/active/modules/100/dirsrv-admin
/var/lib/selinux/targeted/active/modules/100/mip6d
/var/lib/selinux/targeted/active/modules/100/piranha
/var/lib/selinux/targeted/active/modules/100/sge
/var/lib/selinux/targeted/active/modules/100/smsd
/var/lib/selinux/targeted/active/modules/100/mirrormanager
/var/lib/selinux/targeted/active/modules/100/kmscon
/var/lib/selinux/targeted/active/modules/100/naemon
/var/lib/selinux/targeted/active/modules/100/rolekit
/var/lib/selinux/targeted/active/modules/100/pkcs11proxyd
/var/lib/selinux/targeted/active/modules/100/rkt

and then my second guess is that after that if you reinstall container-selinux
and passt-selinux, it should install without an error.

if so, you can do `touch /etc/selinux/.autorelabel`, reboot and then do `ls
-alZ /usr/bin/crun` it should show `container_runtime_exec_t` and the container
stuff should work again

but these are just assumptions, since i can not reproduce the issue and also
dont have access to the system. also i am still pretty unsure what exactly
happened there, so please take it with a grain of salt :)