Recent content by dasunsrule32

  1. D

    ipcc_send_rec[1] failed: Unknown error -1

    When you add unauthenticated, are you saying root? I have passwordless sudo enabled for the user. Is there a feature request open for this to work with normal users already? I can submit one if not.
  2. D

    ipcc_send_rec[1] failed: Unknown error -1

    I'm trying to figure this out still because it breaks using sudo and a normal user, especially when using auto completion.
  3. D

    PVE 9 - NVIDIA Container Toolkit Broken

    If you're having issues with this then either deploy a VM with Docker in it or look for alternative install methods other than Docker. I can't help with this as I don't use Frigate, I'd take that to their forums/communities for help. Good luck!
  4. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Also, make sure you can run nvidia-smi in the container.
  5. D

    PVE 9 - NVIDIA Container Toolkit Broken

    I'm assuming this is docker? If so, you need to install the nvidia container toolkit in the container. # nvidia for docker with nvidia-container-toolkit on the PVE host: curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | gpg --dearmor -o...
  6. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Can you post the config of the LXC?
  7. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Even with the driver, privileged still isn't needed. You just have to set the card permissions on the /dev/nv* stuff in the container config. This is how we all learn though! You got this!
  8. D

    PVE 9 - NVIDIA Container Toolkit Broken

    You don't need privileged for Docker. My config above actually will work with Docker as well. Only thing you really need to do is just map permissions to the correct mapped permissions, root for example: 100000:100000 if you're doing bind mounts to your data on the local host. Example of some...
  9. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Also, the hook will only work with unprivileged containers. So you'd need to continue the driver route if are using privileged containers.
  10. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Make a backup and do not use the nvidia hook until you uninstall the manually installed driver. Run the installer and uninstall the drivers, then you "should" be able to use the bind mound options in the config, delete the card permissions as well. You don't need to handle the card permissions...
  11. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Nope, no need for driver installation. The drivers from the host get bind mounted to the container from the host for use. You can see I outputted the mount output there. See my post further up: https://forum.proxmox.com/threads/pve-9-nvidia-container-toolkit-broken.169364/post-797860
  12. D

    PVE 9 - NVIDIA Container Toolkit Broken

    This is what I'm using on pve9 for the toolkit: cat /etc/apt/sources.list.d/nvidia-container-toolkit.sources Types: deb URIs: https://nvidia.github.io/libnvidia-container/stable/deb/amd64/ Suites: / Components: Signed-By: /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg I think lxc-pve...
  13. D

    PVE 9 - NVIDIA Container Toolkit Broken

    Your way works, and I used that as a workaround when the nvidia hook was broken, but that's an awful lot of work. Just Install the nvidia-container-toolkit and nvidia drivers on the host and add these lines to your container's config: lxc.hook.pre-start: sh -c '[ ! -f /dev/nvidia0 ] &&...