I am new to this device, i looked at it as part of enabling AI detection in Frigate on TrueNAS which blocks install of drivers (the solution i built addresses that)
The one thing that surprised me is the need for privileged containers (and i see from the forum same is true for LXC) for running on frigate.
This will be a barrier to adoption (for example the native truenas frigate app can not be set to privileged, yes i know one can run a customer docker compose - thats not the point).
I am unclear the root issue here - the way MemryX architecture works or a flaw in frigates support?
Maybe someone can explain the reason and if there are any mitigations.
You don’t need privileged. If you look at the official thread on privileged lxc (PROXMOX), you will see my comment explaining how to make it work unprivileged. It’s pretty simple - only a couple changes from the instructions. I can’t advise for TrueNAS (I don’t use it). But my solution works fine for proxmox unprivileged lxc and I’ve been using it since the day I made that comment.
i am not using LXCs, the instructions say otherwise, maybe post a link to the updated instructions to help others as the link you shared says at the top ‘create privileged LXC’ … so not sure how that was helpful!