Skip to content
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

Current user does not have read permissions on /dev/dri/renderD128 #519

Closed
travisboss opened this issue Mar 24, 2023 · 4 comments
Closed
Labels
needs triage To be triaged

Comments

@travisboss
Copy link

Describe the bug
A clear and concise description of what the bug is.

Current user does not have read permissions on /dev/dri/renderD128

To Reproduce
Steps to reproduce the behavior:

sudo docker exec -it nextcloud occ memories:video-setup

Screenshots
If applicable, add screenshots to help explain your problem.

Platform (please complete the following information):

  • OS: Ubuntu Server 20.04
  • Browser N/A
  • Version N/A

Additional context
Add any other context about the problem here.

Using the linuxserver/nextcloud container

added dev/dri and required packages to be installed, have verified my user 1000 and 100 have access to the group render and video.

  nextcloud:
    image: lscr.io/linuxserver/nextcloud
    container_name: nextcloud
    devices:
      - /dev/dri:/dev/dri
    environment:
      - PUID=${PUID} #change PUID if needed
      - PGID=${PGID}  #change PGID if needed
      - TZ=${TZ} #change Time Zone if needed
      - DOCKER_MODS=linuxserver/mods:universal-package-install
      - INSTALL_PACKAGES=libva|libva-intel-driver|intel-media-driver|mesa-va-gallium
    volumes:
      - ./nextcloud:/config
      - /pool/storage/nextcloud:/data
    depends_on:
      - mariadb
    restart: unless-stopped

Important: Are all of the following are true?

  • I have followed the configuration steps.
    True
  • I am NOT using OCCWeb to run occ commands
    True
  • The problem persists after clearing browser cache
    N/A
@travisboss travisboss added the needs triage To be triaged label Mar 24, 2023
@travisboss
Copy link
Author

Starting ffmpeg feature detection
This may take a while. Please be patient

Downloading test video file ... OK

Attempting to start go-vod ... OK
go-vod logs will be stored at: /tmp/go-vod/ocp61gswjh00.log

Testing transcoding with CPU ... OK

Checking for VAAPI acceleration (/dev/dri/renderD128) ... OK
Checking for permissions on /dev/dri/renderD128 ... NO
Current user does not have read permissions on /dev/dri/renderD128
VAAPI will not work. You may need to add your user to the video/render groups

Checking for NVIDIA acceleration with NVENC
Testing transcoding with NVENC (scale_npp) ... FAIL
Testing transcoding with NVENC (scale_cuda) ... FAIL
NVENC does not seem to be available

Feature detection completed

Transcoding and HLS are now enabled! Monitor the log file for any errors
You should restart the server for changes to take effect

@starlingfire
Copy link

starlingfire commented Mar 24, 2023

@travisboss I was able to resolve the VAAPI permission error by adding the user www-data to the group that owns /dev/dri/renderD128. For me it was the group render.

Check the owner and group permissions of the device:

ls -la /dev/dri

drwxr-xr-x  3 root root        100 Mar 24 14:38 .
drwxr-xr-x 18 root root       4240 Mar 24 14:38 ..
drwxr-xr-x  2 root root         80 Mar 24 14:38 by-path
crw-rw----  1 root video  226,   0 Mar 24 14:38 card0
crw-rw----  1 root render 226, 128 Mar 24 14:38 renderD128

Add the user running Nextcloud to that group

usermod -a -G render www-data

I'm now getting HTTP 408 errors when running memories:video-setup but it's a step forward at least.

Edit: I don't have an Intel card so I don't know why I'm wasting my time getting VAAPI working 🤣. I just turned off transcoding and now I can watch videos.

Source: dlandon/zoneminder.machine.learning#105

@locdenz
Copy link

locdenz commented Mar 25, 2023

@travisboss I faced the same issue, I found 2 options.

The easiest one is creating a cron job running at reboot to change permissions of that file.
@reboot chmod 777 /dev/dri/*

Or follow this thread to create a file /etc/cont-init.d/50-gid-video within container.
linuxserver/docker-plex#207

@travisboss
Copy link
Author

@pulsejet are you able to check the http 408 issue? It looks like myself and another user are also having that same issue.

cc @starlingfire

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage To be triaged
Projects
None yet
Development

No branches or pull requests

4 participants