The fixed user seems to lose other groups
felipecrs opened this issue · 6 comments
If the user is part of more groups than the dockergroup
(the group which fixuid changes), those groups do not get applied in the new user.
Secondary groups are specified in /etc/groups
in the 4th column, which is referenced by username
In the case the container is run with the UID of an existing user that does not match the name of the configured fixuid user, the UID is not changed, so secondary groups will not match:
Lines 138 to 147 in 4467c25
But in the typical case that the container is run with a UID that does not match any user in /etc/passwd
, the UID of the configured fixuid user will be changed, but the secondary groups from /etc/group
will still match, since they are referenced by username
@caleblloyd so sorry, but I didn't understand much of your reply.
I'm back to say that, if a group is required to be present you can ensure its presence with docker run --group-add <group-name>
, in my case docker run --group-add=docker
.
This issue is still present.
Even if user
is part of secondary groups in /etc/group, the user's groups only reflect what is set in /etc/fixuid/config.yml. You can verify this by running groups
Running with @felipecrs workaround will make the group present in the output of groups
The problem lies in the ExitOrExec function that is executing the next process after doing all the changes. It is setting the euid and egid, but not looking up and setting additional groups from /etc/group from inside the container.
With this fix I was able to greatly simplify fixdockergid
and drop the dependency on setpriv
for it. Thanks a lot!