podman: Containers fails to start if SELinux policy is not defining the correct types
Hello,
On debian unstable (podman 3.0.1), with SELinux enabled and running the refpolicy (I disabled the virt
module for some reasons) in permissive mode, podman is not able to start a container. If I reboot and disabled SELinux, everything works fine.
podman just fails (as root or non-root user) with:
Error: failed to mount shm tmpfs "/home/bigon/.local/share/containers/storage/overlay-containers/99d002d974978230de6e6214d41c4f9b24f4d054f7d58b7b7cc6729adddcc7ec/userdata/shm": invalid argument
If SELinux is in permissive podman should probably just ignore that and continue. In any case, it should log it instead of displaying a cryptic error
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (10 by maintainers)
container_t should not be hard coded anywhere in podman, and I do find it anywhere. The type comes from either: /usr/share/containers/selinux/contexts, which is defined in the container-selinux package, which should define conainer_t.
Or it is coming from /etc/selinux/targeted/contexts/lxc_contexts
Where are you getting it from?