Missing file capabilities (setcap, getcap) in TurrisOS 5 on ext4 filesystem
I'm hitting the same error as #223 but (I think) for a different cause.
I reinstalled my Turris Omnia from TurrisOS 3.11.x (the latest available) to TurrisOS 5.1.9 with a new installation from scratch (I didn't tried to upgrade). I have the NAS box setup with two HDD in mdadm raid 1 on top of which I have several lvm volumes all formatted with ext4 filesystem. The different filesystems were created with a previous TurrisOS version (3.10 or 3.11, I don't know).
When I run
getcap command in an lxc container (in one of the previously mentioned ext4 FS) I always get the
Failed to get capabilities of file '/bin/ping' (Operation not supported) error.
I checked that the kernel support ACL for ext4:
# zcat /proc/config.gz | grep ACL CONFIG_EXT4_FS_POSIX_ACL=y # CONFIG_REISERFS_FS_POSIX_ACL is not set CONFIG_JFS_POSIX_ACL=y CONFIG_XFS_POSIX_ACL=y CONFIG_BTRFS_FS_POSIX_ACL=y # CONFIG_F2FS_FS_POSIX_ACL is not set CONFIG_FS_POSIX_ACL=y # CONFIG_TMPFS_POSIX_ACL is not set CONFIG_HFSPLUS_FS_POSIX_ACL=y # CONFIG_JFFS2_FS_POSIX_ACL is not set # CONFIG_NFS_V3_ACL is not set # CONFIG_NFSD_V3_ACL is not set CONFIG_CIFS_ACL=y
and that the filesystem is mounted with correct options:
# grep lxc /proc/mounts /dev/mapper/vg_router-lxc /srv/lxc ext4 rw,relatime,data=ordered 0 0 # tune2fs -l /dev/mapper/vg_router-lxc | grep -E 'features|options|state' Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Default mount options: user_xattr acl Filesystem state: clean
I tried to create
- container on old created ext41 -> fails
- container on newly created ext42 -> fails
- container on btrfs -> no error
So it seems to come from the ext4 filesystem and TurrisOS 5.9 combination (I never hit this issue with TurrisOS 3).
@kkoci Any clue on that?