You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A change to openSUSE's NVIDIA graphics driver kernel module package that can be traced back to release 550.120 results in a naming convention alteration to the Vulkan ICD configuration file, from nvidia_icd.json to nvidia_icd.%{_target_cpu}.json.
The consequence of this is that any distrobox container created using --nvidia will be unable to utilize Vulkan within the guest container due to the missing ICD configuration file.
As far as my understanding goes, the change is valid due to an update to the ICD loader specification where the expected file pattern is vendor_icd.target_cpu.json. The specification was updated to avoid conflict where both i686 and x86_64 Vulkan libraries are utilized on the same system, Mesa drivers are also using the same pattern from what I can see.
To Reproduce
Create a container with NVIDIA driver host integration: distrobox-create -n test --nvidia
Enter the container: distrobox-enter test
Install the Vulkan tools package: sudo zypper install --no-recommends vulkan-tools
Verify integrity of Vulkan: vulkaninfo --summary and/or vkcube
Expected behavior
vulkaninfo --summary to return Vulkan information summary.
vkcube to render the 3D cube verifying a successful Vulkan install.
Logs
vulkaninfo --summary output:
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_MESA_device_select uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR at /home/abuild/rpmbuild/BUILD/Vulkan-Tools-1.4.304/vulkaninfo/./vulkaninfo.h:247:vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED
vkcube output:
Selected WSI platform: xcb
vkEnumeratePhysicalDevices reported zero accessible devices.
Do you have a compatible Vulkan installable client driver (ICD) installed?
Please look at the Getting Started guide for additional information.
Desktop (please complete the following information):
Are you using podman, docker or lilipod? podman
Which version or podman, docker or lilipod? podman version 5.3.2
Which version of distrobox? distrobox: 1.8.1.2
Which host distribution? openSUSE Tumbleweed 20250209
How did you install distrobox? sudo zypper install --no-recommends distrobox
Additional context
The naming convention has also been amended in the equivalent Fedora package and I would suspect in other Linux distributions too.
The text was updated successfully, but these errors were encountered:
m4nn
changed the title
[Error] ICD loader specification update breaks Vulkan inside distrobox containers when using NVIDIA driver host integration (OpenSUSE and Fedora)
[Error] ICD loader specification update breaks Vulkan inside distrobox containers when using NVIDIA driver host integration (openSUSE and Fedora)
Feb 13, 2025
m4nn
pushed a commit
to m4nn/distrobox
that referenced
this issue
Feb 14, 2025
Describe the bug
A change to openSUSE's NVIDIA graphics driver kernel module package that can be traced back to release 550.120 results in a naming convention alteration to the Vulkan ICD configuration file, from
nvidia_icd.json
tonvidia_icd.%{_target_cpu}.json
.The consequence of this is that any distrobox container created using
--nvidia
will be unable to utilize Vulkan within the guest container due to the missing ICD configuration file.As far as my understanding goes, the change is valid due to an update to the ICD loader specification where the expected file pattern is
vendor_icd.target_cpu.json
. The specification was updated to avoid conflict where both i686 and x86_64 Vulkan libraries are utilized on the same system, Mesa drivers are also using the same pattern from what I can see.To Reproduce
distrobox-create -n test --nvidia
distrobox-enter test
sudo zypper install --no-recommends vulkan-tools
vulkaninfo --summary
and/orvkcube
Expected behavior
vulkaninfo --summary
to return Vulkan information summary.vkcube
to render the 3D cube verifying a successful Vulkan install.Logs
vulkaninfo --summary
output:vkcube
output:Desktop (please complete the following information):
podman
podman version 5.3.2
distrobox: 1.8.1.2
openSUSE Tumbleweed 20250209
sudo zypper install --no-recommends distrobox
Additional context
The naming convention has also been amended in the equivalent Fedora package and I would suspect in other Linux distributions too.
The text was updated successfully, but these errors were encountered: