Expand smoke testing to include SELinux

[MoralCode]

ah ok, based on slack conversation and the outputs of ls -alZ docker/rabbitmq, it seems like this points to docker rootful daemon (the default config) by default using a label of system_u:object_r:container_file_t:s0:cXXX,cYYY (container_file_t having been added by this fix).

This seemingly isn't affecting podman because it runs as rootless by default and has some defaults that let it read files in the users homedir.

This likely isn't affecting the CI because I doubt SELinux is enabled in the CI.

So yeah SELinux + docker compatibility with our stock config does seem to be a gap in our testing.

Originally posted by @MoralCode in #508 (comment)

[MoralCode]

i think in order to avoid doubling the number of large jobs we run on each PR,it may be better to move the smoke tests over to having SELinux enabled for both images (since its probably a stricter environment to test under and if it works under SELinux, it should (i hope) also work in a less restrictive non-SELinux environment

[dcermak]

i think in order to avoid doubling the number of large jobs we run on each PR,it may be better to move the smoke tests over to having SELinux enabled for both images (since its probably a stricter environment to test under and if it works under SELinux, it should (i hope) also work in a less restrictive non-SELinux environment

it should, but the problem is going to be to get a SELinux enabled CI worker. Afaik the default github runners are restricted to Ubuntu, which only has Apparmor. Enabling SELinux there is afaik not possible

[MoralCode]

ah yeah that would be a problem. I guess this'll have to wait until we can get some more automated testing for the fedora side of things