Timeline for Docker with device [GPIO] access while running as a specified user that is not `root`
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2023 at 1:35 | comment | added | Kent Gibson | As noted in @Rob's answer, you don't need the udev rule - docker is just mounting the host /dev in the container. But leaving the comment for reference for anyone unsure where the group/permissions of the gpiochip are generally set on the host. | |
| Jul 6, 2023 at 10:07 | vote | accept | Rob | ||
| Jul 5, 2023 at 14:46 | comment | added | Kent Gibson |
Oh, and you don't need /sys to use libgpiod - in case that is the reason you are importing it into the docker container.
|
|
| Jul 5, 2023 at 14:40 | comment | added | Kent Gibson |
I think the rules you need are in /etc/udev/rules.d/99-com.rules in Raspberry Pi OS, specifically the SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660" rule.
|
|
| Jul 5, 2023 at 13:43 | comment | added | Rob |
That's an excellent suggestion: before I made test_user a member of just the root group on the host-side in the post above, it was actually a member of the gpio group, however there isn't a gpio group inside the Ubuntu Docker container; I guess I need to do some udev rules magic, a la unix.stackexchange.com/questions/42122/…?
|
|
| Jul 5, 2023 at 10:01 | history | edited | Kent Gibson | CC BY-SA 4.0 |
improved formatting
|
| Jul 5, 2023 at 9:54 | history | edited | Kent Gibson | CC BY-SA 4.0 |
provide working example
|
| Jul 5, 2023 at 9:32 | history | answered | Kent Gibson | CC BY-SA 4.0 |