diff options
author | Matthew Heon <matthew.heon@pm.me> | 2020-09-18 11:51:55 -0400 |
---|---|---|
committer | Matthew Heon <matthew.heon@pm.me> | 2020-09-18 13:54:25 -0400 |
commit | 2f605dcc1c05c1081537a8eaf56ad256fb0c050c (patch) | |
tree | 642c385b9a94dd73dcefa45d487d37da6626b42e /pkg | |
parent | fd7cdb25027bb33c33eacb99f1a02838eca5d684 (diff) | |
download | podman-2f605dcc1c05c1081537a8eaf56ad256fb0c050c.tar.gz podman-2f605dcc1c05c1081537a8eaf56ad256fb0c050c.tar.bz2 podman-2f605dcc1c05c1081537a8eaf56ad256fb0c050c.zip |
Preserve groups in exec sessions in ctrs with --user
Podman wants to guarantee that exec sessions retain the groups of
the container they are started in, unless explicitly overridden
by the user. This guarantee was broken for containers where the
`--user` flag was specified; this patch resolves that.
Somewhere in the Exec rewrite for APIv2, I changed the location
where the container's User is passed into the exec session
(similar to groups, we also want to preserve user unless
overridden). The lower-level Exec APIs already handled setting
user and group appropriately if not specified when the exec
session was created, but I added duplicate code to handle this
higher in the stack - and that code only handled setting user,
not supplemental groups, breaking support in that specific case.
Two things conspired to make this one hard to track down: first,
things were only broken if the container explicitly set a user;
otherwise, the container user would still appear to be unset to
the lower-level code, which would properly set supplemental
groups (this tricked our existing test into passing). Also, the
`crun` OCI runtime will add the groups without prompting, which
further masked the problem there. I debated making `runc` do the
same, but in the end it's better to fix this in Podman - it's
better to be explicit about what we want done so we will work
with all OCI runtimes.
Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'pkg')
0 files changed, 0 insertions, 0 deletions