Replies: 2 comments 2 replies
-
This issue has been bugging me so I dug into it... Changing the value of You can check the current value of your perf_event_paranoid flag by running this in the host shell: sysctl -a | grep kernel.perf_event_paranoid This will add it to your config and apply the change: echo kernel.perf_event_paranoid=0 >> /etc/sysctl.d/local.conf
sysctl --system This is mentioned in the Frigate docs here, but they recommend setting it to 2, which did not work for me. Related note:On my host machine, the Intel iGPU will be at either I removed the device mapping to I'd be curious to know if this works for other users and apps or if it causes problems. If it works, we might not need the part of this code that adds them. HTH, |
Beta Was this translation helpful? Give feedback.
-
Awesome, that indeed took away the error and it seems to work. I don't recognize the card0/card1 behavior, it is always card1 at my machine. |
Beta Was this translation helpful? Give feedback.
-
By accident I installed the Frigate LXC as an unpriviliged container. I added an extra device to the config file to redirect my Coral TPU:
And almost everything seems to work fine. The only significant error I currently see is
my guess this has something to do with the mapping of the GPU to the LXC and should be fixable.
So, are there any other reasons to run Frigate in a priviliged lxc?
Beta Was this translation helpful? Give feedback.
All reactions