[HW Accel Support]: Device not mapping properly? #13128
-
Describe the problem you are havingI can't enable hardware acceleration for my cameras. Whenever I tried to enable hardware acceleration, the cameras would stop working and the app would start to hang. When I disable hardware acceleration the cameras start working again. While trying to find out why this was happening I noticed the device specified in the Docker compose file wasn't being mapped to the container. I'm not sure if I'm missing some setup (maybe related to docker or permissions?) but any help is appreciated. Output of Version0.14.0-da913d8 Frigate config filemqtt:
enabled: false
detectors:
ov:
type: openvino
device: GPU
cameras:
cam1:
enabled: true
ffmpeg:
inputs:
- path: rtsp://camerapath
roles:
- detect
hwaccel_args: preset-vaapi
detect:
enabled: false
width: 1280
height: 720
version: 0.14docker-compose file or Docker CLI commandservices:
frigate:
container_name: frigate
privileged: true
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "128mb" # 2 FHD cams
devices:
# - /dev/bus/usb:/dev/bus/usb # Passes the USB Coral, needs to be modified for other versions
- /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- ./config:/config
- /media/frigate:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "8971:8971"
# - "5000:5000" # Internal unauthenticated access. Expose carefully.
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "password"Relevant log output2024-08-16 16:19:58 frigate | 2024-08-16 22:19:58.756516127 [2024-08-16 22:19:58] frigate.app INFO : Capture process started for cam1: 393
2024-08-16 16:20:01 frigate | 2024-08-16 22:20:01.247092819 [2024-08-16 22:20:01] frigate.video ERROR : cam1: Unable to read frames from ffmpeg process.
2024-08-16 16:20:01 frigate | 2024-08-16 22:20:01.247295432 [2024-08-16 22:20:01] frigate.video ERROR : cam1: ffmpeg process is not running. exiting capture thread...FFprobe output from your cameraffprobe version 5.1.6-0+deb12u1 Copyright (c) 2007-2024 the FFmpeg developers
built with gcc 12 (Debian 12.2.0-14)
configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
libavutil 57. 28.100 / 57. 28.100
libavcodec 59. 37.100 / 59. 37.100
libavformat 59. 27.100 / 59. 27.100
libavdevice 59. 7.100 / 59. 7.100
libavfilter 8. 44.100 / 8. 44.100
libswscale 6. 7.100 / 6. 7.100
libswresample 4. 7.100 / 4. 7.100
libpostproc 56. 6.100 / 56. 6.100
Input #0, rtsp, from 'rtsp://camerapath':
Metadata:
title :
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709, progressive), 1920x1080, 15 fps, 14.99 tbr, 90k tbn
Stream #0:1: Audio: aac (LC), 8000 Hz, mono, fltpOperating systemDebian Install methodDocker Compose Network connectionMixed Camera make and modelSwann SWIFI-PTCAM2 Any other information that may be helpfulI'm running Frigate on a Beelink EQ12 with 16GB RAM and an Intel N100 CPU and iGPU. Installed Docker Desktop and set up Frigate using docker compose. |
Beta Was this translation helpful? Give feedback.
Answered by
NickM-27
Aug 16, 2024
Replies: 1 comment 5 replies
-
|
might be an issue with docker desktop, are you sure you applied the docker compose file after editing it? |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Hello. Yes, I ran |
Beta Was this translation helpful? Give feedback.
-
|
seems like it might be an issue with docker desktop, the getting started guide recommends installing it from the docker engine https://docs.frigate.video/guides/getting_started#install-docker |
Beta Was this translation helpful? Give feedback.
Answer selected by
StrScr
-
|
Alright, I'll try uninstalling docker desktop and starting again with docker engine. I'll post an update if anything changes. |
Beta Was this translation helpful? Give feedback.
-
|
Well, the good news is the device is now getting mapped correctly! On the other hand, my container now keeps restarting over and over, so using the web app is almost impossible. I think this is an unrelated problem, but I'm not sure. I'm including the logs here. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that other problem was indeed unrelated. It was a matter of finishing setting up detection, recording and everything else and now Frigate is working A-OK. It's a bit weird that docker desktop somehow was the culprit, I was under the impression it was the same as docker engine, just with some extras. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
seems like it might be an issue with docker desktop, the getting started guide recommends installing it from the docker engine https://docs.frigate.video/guides/getting_started#install-docker