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

Issues with Agent DVR Docker Container After Update on Unraid #767

Open
44jonas44 opened this issue Dec 10, 2024 · 1 comment
Open

Issues with Agent DVR Docker Container After Update on Unraid #767

44jonas44 opened this issue Dec 10, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@44jonas44
Copy link

Affected Version: 5.8.4.0

Hi everyone,

I’ve been running Agent DVR in a Docker container on Unraid successfully for some time now. However, after a recent Docker update, the container started throwing errors, and I can’t get it to work anymore. Here’s a summary of the problem:
Setup:

Host OS: Unraid (fully updated).

Docker Image: doitandbedone/ispyagentdvr.

Hardware: AMD GPU (using /dev/dri for hardware acceleration).

Docker Run Command:

Also tried host as Network Type

docker run -d --name='Agent-DVR' --net='bridge' --pids-limit 2048 --privileged=true \
-e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ChlorClown" \
-e HOST_CONTAINERNAME="Agent-DVR" \
-p '8090:8090/tcp' -p '3478:3478/udp' -p '50000:50000/tcp' \
-v '/mnt/user/appdata/agentDVR/config':'/agent/Media/XML/':'rw' \
-v '/mnt/user/Aufnahmen/':'/agent/Media/WebServerRoot/Media/':'rw' \
-v '/mnt/user/appdata/agentDVR/commands':'/agent/Commands':'rw' \
--device='/dev/dri' 'doitandbedone/ispyagentdvr'  

The Issue:

After updating the Docker image, the container fails with GPU-related errors:

From the Docker logs: The Issue:After updating the Docker image, the container fails with GPU-related errors:

From the Docker logs:implib-gen: libva.so.2: failed to resolve symbol 'vaMapBuffer2' via dlsym: /lib/x86_64-linux-gnu/libva.so.2: undefined symbol: vaMapBuffer2 amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description. If they do, bad things may happen!

It worked for over 1,5 years with that GPU, but now after the Update i cant get it to run again. If i remove the GPU it works again, but with no gpu encoding of course, but i have to use it.

The docker has acces to the GPU

# ls -l /dev/dri
total 0
crw-rw---- 1 root 18 226,   0 Dec 10 22:00 card0
crwxrwxrwx 1 root 18 226, 128 Dec 10 22:00 renderD128

Steps To Reproduce
Steps to reproduce the behavior:
Using GPU /dev/dri

Expected behavior
Maybe check libversions

Reproduction rate
100%

@44jonas44 44jonas44 added the bug Something isn't working label Dec 10, 2024
@ispysoftware
Copy link
Collaborator

I responded to you on reddit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants