[Bugs] [Bug 764245] [FEAT] glusterfs requires CAP_SYS_ADMIN capability for "trusted" extended attributes - container unfriendly

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=764245

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |Triaged
             Status|ASSIGNED                    |NEW
            Version|3.1.2                       |mainline
           Assignee|vbellur at redhat.com          |bugs at gluster.org
            Summary|[FEAT] glusterfs requires   |[FEAT] glusterfs requires
                   |CAP_SYS_ADMIN capability    |CAP_SYS_ADMIN capability
                   |for "trusted" extended      |for "trusted" extended
                   |attributes - virtualization |attributes - container
                   |unfriendly                  |unfriendly



--- Comment #3 from Niels de Vos <ndevos at redhat.com> ---
Using containers to host bricks requires writing the "trusted.*" xattrs to the
underlaying filesystem. The brick processes need to have the CAP_SYS_ADMIN
capability (see: man 7 capabilities). Containers are expected to have little
privileges, and grating CAP_SYS_ADMIN to a container is frowned upon.

Proposed solution:
- instead of using "trusted.*" xattrs on the bricks, use "user.*" xattrs

Implementation details/notes/ideas:
- provide a volume or mount option to specify that "user.*" should be used
- it is impractical (and would hurt compatibility) when all the xattrs would be
  replaced by "user.*" throughout the whole sources. It would be simpler and
more
  compatible to have the posix-xlator handle the volume/mount option. A
fallback
  on checking for the other xattr prefix would be more efficient there too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.