… and why did it take so long for that to happen? If you build Toolbx from Git and install it to your usual prefix on a host operating system with the proprietary NVIDIA driver, then you will…
Toolbx now supports the use of the proprietary NVIDIA driver in containers without the need to recreate them or use special options. This is achieved through the use of NVIDIA Container Toolkit to generate a Container Device Interface specification on the host, which is then shared with the Toolbx container’s entry point. The use of “nvidia-ctk” and “podman create” is not currently implemented due to root access requirements and the inability to update existing containers. The delay in enabling this support was due to the need for hardware access for testing, which was facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU.
Toolbx now supports proprietary NVIDIA driver in containers
NVIDIA Container Toolkit generates Container Device Interface specification on the host
Use of "nvidia-ctk" and "podman create" not implemented due to root access requirements and inability to update existing containers
Delay in enabling support was due to the need for hardware access for testing, facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU
According to tldr.chat:
Toolbx now supports the use of the proprietary NVIDIA driver in containers without the need to recreate them or use special options. This is achieved through the use of NVIDIA Container Toolkit to generate a Container Device Interface specification on the host, which is then shared with the Toolbx container’s entry point. The use of “nvidia-ctk” and “podman create” is not currently implemented due to root access requirements and the inability to update existing containers. The delay in enabling this support was due to the need for hardware access for testing, which was facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU.