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
In the current spec, .process.user.gid is defined as a REQUIRED attribute.
I suggest makng this attribute OPTIONAL to allow retaining overflowgid, by avoiding calling setgroups(2).
When gid is unset, additionalGids MUST be unset, too.
This is useful for exposing crw-rw---- devices to Rootless Containers:
I have issues mounting a device with rootless docker through --device /dev/ttyUSB0. The device is accessible outside the docker to users of the dialout group. But I suspect the group is not properly propagated to the docker container. The device shows up as
crw-rw---- 1 nobody nogroup 188, 0 Nov 15 15:59 /dev/ttyUSB0
within the docker. On the host it is
crw-rw---- 1 root dialout 188, 0 Nov 15 07:59 /dev/ttyUSB0
Trying to access the device leads to a Permission denied error.
The text was updated successfully, but these errors were encountered:
https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config.md
In the current spec,
.process.user.gid
is defined as aREQUIRED
attribute.I suggest makng this attribute
OPTIONAL
to allow retainingoverflowgid
, by avoiding callingsetgroups(2)
.When
gid
is unset,additionalGids
MUST be unset, too.This is useful for exposing
crw-rw----
devices to Rootless Containers:dialout
group moby/moby#43019The text was updated successfully, but these errors were encountered: