system group creation for android container device access needs to move out of the build scripts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
New
|
High
|
Unassigned |
Bug Description
currently live-build/
in android kernel, drivers and binary userspace tools are using a hardcoded GID -> groupname mapping to manage device access
http://
it currently seems like we have to have at least a minimal set of these groups on the ubuntu side to have sockets and /dev entries mapped to the hardcoded GIDs the android side expects for granting access.
when discussing this migration the foundations team had massive concerns about using such a hardcoded mapping on the ubuntu side. while this bug is easily fixed by moving the script to the right package, further discussion is needed to find a conceptual solution that suits all parties and does not break devcie access and socket communication with android services.
Changed in livecd-rootfs (Ubuntu): | |
status: | Triaged → In Progress |
Changed in livecd-rootfs (Ubuntu): | |
status: | In Progress → New |
subscribed canonical- foundations and the phone foundations teams since this requires discussion across both