Toolbox unusable: failed to apply mount from Container Device Interface for NVIDIA

[BraSDon]

Describe the bug

When trying to enter any one of my toolboxes after a ujust update, I get the following error message and can not enter my toolbox.

Error: mount: /run/nvidia-persistenced/socket: mount point does not exist. dmesg(1) may have more information after failed mount system call. failed to apply mount from Container Device Interface for NVIDIA

In dmesg I found the following related output:
[ 7.955215] systemd[1]: /usr/lib/systemd/system/nvidia-persistenced.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/nvidia-persistenced/nvidia-persistenced.pid → /run/nvidia-persistenced/nvidia-persistenced.pid; please update the unit file accordingly.

What did you expect to happen?

I expected to be able to enter my toolboxes.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:b50643cf9d9d9600acb7e5d1824d575659441b71b44374e146b4429172c5439d
Version: 40.20241020 (2024-10-21T05:07:34Z)
LayeredPackages: git go neovim

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:a187a0daf0a5301457e2e8e5441c9646bd9c6891a6c03bbccc86b1c13735c2e7
Version: 40.20241014 (2024-10-15T09:00:28Z)
LayeredPackages: git go neovim

Hardware

Operating System: Bazzite 40
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-210.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Manufacturer: MSI
Product Name: MS-7A63
System Version: 1.0

Extra information or context

Based on the related dmesg, I thought about updating /usr/lib/systemd/system/nvidia-persistenced.service accordingly. However, I dont want to break things and rather consult with others first.
As a hotfix, I performed a rpm-ostree rollback.

[BraSDon]

Upstream issue exists and is being resolved: containers/toolbox#1572