-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/dev/dri/renderD128 owned by "render" group on some hosts #105
Comments
@nattvard Could you please tell me how you got HW acceleration to work? Did you have to install |
I had to add command:
|
I have been investigating this and found a really elegant solution to the permissions issue that the guys over at linuxserver used for their Plex image. The script is a direct clone of their version, I have just added some echos to show what is going on and changed the user to the www-data one we use for ZoneMinder. It adds the www-data user to the appropriate group(s) if they already exist or creates new groups as required. To apply this workaround, add this to your user script:
I'm going to raise a PR with dlandon and see if he/she wants to roll this approach into the build. |
Opened a PR here: #146 |
Fixed in the next release. |
I'm using Intel VAAPI to enable hardware acceleration on decoding the streams. For this to work,
/dev/dri/
must be available to the container, and thewww-data
user must be in the group owning/dev/dri/renderD128
.In newer versions of Ubuntu (19+ ?)
/dev/dri/renderD128
is owned byrender
instead ofvideo
.www-data
is added tovideo
, but not to therender
group (that doesn't exist). As seen below, the render group 109 is not known inside the container.Host ownership:
Container ownership:
$ docker exec zoneminder ls -l /dev/dri total 0 crw-rw---- 1 root video 226, 0 Jul 7 16:20 card0 crw-rw---- 1 root 109 226, 128 Jul 7 16:20 renderD128
The groups of www-data inside the container:
My fix to this was to create the render group and add the www-data user to it in
userscript.sh
:My
docker-compose.yml
:It seems like there was a similar issue with Plex in Docker, as seen here: linuxserver/docker-plex#211
The text was updated successfully, but these errors were encountered: