Add support for NVIDIA open GPU kernel modules and userspace components in gpu-support

[chrisjamesbond]

Currently the IncusOS non primary application gpu-support includes GPU firmware blobs, but does not prevent the nouveau driver from binding to NVIDIA hardware at boot after installation. While it includes the NVIDIA firmware, it lacks the kernel driver and userspace components needed for the nvidia.runtime=true config to function

Ideally gpu-support should also bundle the official NVIDIA Linux Open GPU Kernel Modules pre-compiled for IncusOS, as well as the open source container orchestration libraries (libnvidia-container, nvidia-container-toolkit) and proprietary userspace components (nvidia-smi, libcuda.so, libnvidia-ml.so, libnvcuvid.so, libnvidia-encode.so, etc.)

This feature would benefit users with NVIDIA GPUs, enabling them to use a larger range of official NVIDIA features such as CUDA compute and NVENC.

This issue was created as a follow-up to the discussion on the Linux Containers forum Nvidia drivers not enabled after installing gpu-support

[chrisjamesbond]

Adding a follow-up because @stgraber pointed out there may be limits around the legality of redistributing these libraries.

libnvidia-container and nvidia-container-toolkit are published under the Apache-2.0 license, so no concerns there. The open-gpu-kernel-modules are dual-licensed MIT/GPL so that should also be fine.

For the proprietary userspace components, section 1.1(d) of the NVIDIA Driver License Agreement states:

Distribute the SOFTWARE provided for use with operating system kernels distributed under the terms of an OSI-approved open source license...provided that (i) the binary files thereof are not modified in any way (except for uncompressing of compressed files) and (ii) this Agreement is provided to each SOFTWARE recipient.

Since IncusOS runs a Linux kernel, this clause seems to permit redistribution as long as the EULA is provided to users on install. That said, I Am Not A Lawyer and this should be verified.

[stgraber]

Yeah, we'll probably try to stay clear of anything that requires showing a EULA or similar to an end user as that'd be a pain. Including licenses in the build isn't problematic and we already do that (/usr/share/common-licenses/) bu the fact that it's not actually user accessible, short of manually unpacking the image is probably not ideal :)

@gibmat we should add an API to access the license files on the system, similar to what you get on Android and other platforms with similar lock down.

[gibmat]

@gibmat we should add an API to access the license files on the system, similar to what you get on Android and other platforms with similar lock down.

Created #1019 to specifically handle an API for licenses.