Filesystem UID mapping for user namespaces: yet another shiftfs

Posted Feb 18, 2020 0:50 UTC (Tue) by willy (subscriber, #9762)
In reply to: Filesystem UID mapping for user namespaces: yet another shiftfs by tau
Parent article: Filesystem UID mapping for user namespaces: yet another shiftfs

You want to add an xattr to every file? They're not free, you know

Filesystem UID mapping for user namespaces: yet another shiftfs

Posted Feb 18, 2020 8:12 UTC (Tue) by dezgeg (subscriber, #92243) [Link] (2 responses)

Don't you already get one per file when using something like SELinux?

Filesystem UID mapping for user namespaces: yet another shiftfs

Posted Feb 18, 2020 14:11 UTC (Tue) by Paf (subscriber, #91811) [Link] (1 responses)

Sure, but why add another?

Also, if this is container related, presumably we’d rather not leave container cruft behind on files in a file system that is just being temporarily used.

Filesystem UID mapping for user namespaces: yet another shiftfs

Posted Feb 18, 2020 16:11 UTC (Tue) by dezgeg (subscriber, #92243) [Link]

> Also, if this is container related, presumably we’d rather not leave container cruft behind on files in a file system that is just being temporarily used.

Yes, this is a good point. Also, what would happen if two different containers need to share the same filesystem from host. Or how would one give a read-only filesystem to a container.