Pádraig Brady <[email protected]> writes: > E.g. with podman we get default SELinux context mount options > for /dev/shm and /, resulting in all files getting context like > the following when created: > security.selinux="system_u:object_r:container_file_t:s0:c458,c677" > > However you can't explicitly set that xattr: > > $ touch file > $ setfattr -n "security.selinux" \ > -v "system_u:object_r:container_file_t:s0:c458,c677" file > setfattr: file: Operation not supported > > * tests/mv/part-symlink.sh: Avoid the issue. Note this is new > since v9.12 as mv now warns about xattr ENOTSUP failures. > * tests/misc/xattr.sh: Avoid the issue (which would have > existed before v9.12). > --- > tests/misc/xattr.sh | 5 +++-- > tests/mv/part-symlink.sh | 7 +++++++ > 2 files changed, 10 insertions(+), 2 deletions(-)
Those changes look good. Do you seee tests/cp/capability.sh fail too? It failed in my podman container. I think I have an idea to fix it without skipping the entire test. Collin
