Question to our Fedora Server QA experts.
There are 2 annoying selinux bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1900869
https://bugzilla.redhat.com/show_bug.cgi?id=1900888
They prevent the automatic start of systemd-nspawn containers.
A distinguishing feature of Server is universality and adaptability to local requirements.
Hence the support of not only one mainstream container solution, but also alternatives
(and especially annoying, with Debian selinux it works).
You can work around these bugs easily following the usual SELinux troubleshooting
procedure. You have to add 5 or 6 rules.
I guess troubleshooting can't be that time-consuming and complex. Especially since the
tests for F34 are running anyway?
Not giving up hope
Peter