has anybody experience with podman running container with systemd and SELinux policy for the container? I face an issue here, if the container starts with /sbin/init, the processes running not with the expected type. If container starts with e.g. /entry.sh to start processes in there, it uses the correct type.
So, ps -efZ with systemd container runs as container_init_t, otherwise e.g. as my_service.process
I run it with --systemd=true and --security-opt label=type:my_service.process
Have not found anything I should do different in case of running a container with systemd.
Thanks for any hints, cheers Stefan