Additional support re: non-udev-managed devices

Is there a way to pass non-udev-managed devices into a container? For examples, the NVIDIA kernel driver writes these devices (which aren't monitored via udev, therefore the container doesn't start as udev cannot find them under DEVNAME):

crw-rw-rw- 1 root root 195,   0 Oct 20 13:36 /dev/nvidia0
crw-rw-rw- 1 root root 195,   1 Oct 20 13:36 /dev/nvidia1
crw-rw-rw- 1 root root 195, 255 Oct 20 13:36 /dev/nvidiactl
crw-rw-rw- 1 root root 507,   0 Oct 20 13:34 /dev/nvidia-uvm
crw-rw-rw- 1 root root 507,   1 Oct 20 13:34 /dev/nvidia-uvm-tools

/dev/nvidia-caps:
total 0
cr-------- 1 root root 234, 1 Oct 20 13:36 nvidia-cap1
cr--r--r-- 1 root root 234, 2 Oct 20 13:36 nvidia-cap2

Char nodes 195:(0/1/255) 507(0/1) and 234(1/2).

Please let me know if this request (to allow static/non-udev device nodes) is considered in-scope for this project,

Thank you!

Start by reviewing how container-hotplug discovers udev-managed devices and passes them into Docker containers. Determine where static or non-udev device nodes could be configured, including the listed NVIDIA character-device major and minor numbers; done requires a decided scope and a way to verify those devices are available in the container.