You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.
Currently, the ACI specifies handling for an image to specify the user, group, and supplemental GIDs to use. However one discussion we had was whether group membership in /etc/groups should be automatically picked up from the filesystem. If the user/UID specified matches a valid user, then in addition to the explicit supplemental GIDs, should the groups the user is a member of also be loaded in? In our case, we were looking at simply calling initgroups().
The text was updated successfully, but these errors were encountered:
This seems like a good pattern to me. Ideally if I load an OS which contains /etc/groups I would expect that group to be respected by the container runtime.
Currently, the ACI specifies handling for an image to specify the user, group, and supplemental GIDs to use. However one discussion we had was whether group membership in
/etc/groups
should be automatically picked up from the filesystem. If the user/UID specified matches a valid user, then in addition to the explicit supplemental GIDs, should the groups the user is a member of also be loaded in? In our case, we were looking at simply callinginitgroups()
.The text was updated successfully, but these errors were encountered: