Re:File Permissions: A painful side of Docker (2019)
by Joker_vD on Monday May 31, 2021 @11:30AM
(#27345023)
I can think of basically two solutions:
1) pass user/group names around and resolve them at the destination to UID/GID; 2) ignore them entirely; assign ownership of all newly created files to the currently authenticated user (if authorized).
Are there other ones?
Re:File Permissions: A painful side of Docker (2019)
by fiddlerwoaroof on Monday May 31, 2021 @12:24PM
(#27345668)
3) treat a machine-id/user-id pair as the “real userid”
4) add a remote->local userid mapping feature to your filesystem.
Decades of network filesystem users have had many solutions to that.