The image I'm using is debian:12 (wasn't changed since it was working). I already have the UID/GID thing set up, but that's a different issue. Using a user that's a member (or not) of the gpio group won't cause an issue when loading the library, but when trying to control the pins. This error is different. This error I'm having now happens when loading the python package.What base image are you using for your container?
I have not built any containers that use gpio recently, but I used to use python:3.XX-slim-buster/bullseye but never tried bookworm.
As for --privileged, if you can run your container with the same UID:GID as an OS user that has access to the gpio (a member of gpio), I believe it should not need that flag.
Statistics: Posted by Gumdrop — Wed Jul 31, 2024 8:35 pm