You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a podman rootless container for plex and it maps several nfs mounts on the host as bind volumes for media access purposes.
When attempting to generate a policy with udica with: podman inspect plex | udica -j - plex_container
Udica throws the error: Couldn't create policy: [Errno 2] No such file or directory
Eventually it turned out it the issue was the volume bind mounts to the media I have in the container. If I remove those volume mappings, the udica command completes without errors.
This is on Fedora Server 35 running stock podman 3.4.4 and udica 0.2.6.
Not sure if this is a bug or not. For now my workaround to generate the initial policy was to remove the nfs mounts from the container and attach them afterwards. Is this a known issue for Udica when nfs bind volumes are present on the container?
The text was updated successfully, but these errors were encountered:
JHBoricua
changed the title
Udica throws error when generating policy on containers mapping nfs shares
Error generating policies on containers mapping nfs shares as bind volumes.
Jan 31, 2022
Hi, thank you for reporting the issue. It is definitely a bug. selabel_lookup throws an exception when it encounters "<>" in a context definition and udica doesn't handle that properly.
vmojzis
added a commit
to vmojzis/udica
that referenced
this issue
Apr 29, 2022
Catch exception triggered by selabel_lookup when it encounters file
context definition containing "<<none>>"
Real label of given path may differ from what selable_lookup
(matchpathcon) returns. Udica should allow access to both.
Fixes:
containers#98containers#109
I have a podman rootless container for plex and it maps several nfs mounts on the host as bind volumes for media access purposes.
When attempting to generate a policy with udica with:
podman inspect plex | udica -j - plex_container
Udica throws the error:
Couldn't create policy: [Errno 2] No such file or directory
Eventually it turned out it the issue was the volume bind mounts to the media I have in the container. If I remove those volume mappings, the udica command completes without errors.
This is on Fedora Server 35 running stock podman 3.4.4 and udica 0.2.6.
Here's the inspect output:
Not sure if this is a bug or not. For now my workaround to generate the initial policy was to remove the nfs mounts from the container and attach them afterwards. Is this a known issue for Udica when nfs bind volumes are present on the container?
The text was updated successfully, but these errors were encountered: