-
Notifications
You must be signed in to change notification settings - Fork 468
Description
Describe the bug
I have found that it is not possible for Vulkan apps to access my AMD GPU inside distrobox when I am connected using a GNOME RDP session. However, when I am using the machine locally (i.e. not through RDP) then I do not have this problem.
To Reproduce
- Install distrobox.
- Create a distrobox.
- Install
vulkan-tools
in the distrobox. - Run
vkcube
inside the distrobox and observe that it uses you GPU. - Remotely connect to your machine using an RDP session.
- Run
vkcube
inside the distrobox and observe that it uses LLVMpipe.
Expected behavior
My GPU should still be accessible to Vulkan apps inside the distrobox even when I am remotely connected.
Logs
Run the commands with --verbose
and post the log here as a file upload
Attach also the output of podman logs
or docker logs
, possibly with --latest
flag
Desktop (please complete the following information):
-
Are you using podman, docker or lilipod?
podman -
Which version or podman, docker or lilipod?
5.6.0 -
Which version of distrobox?
1.8.1.2 -
Which host distribution?
OpenSUSE Tumbleweed with GNOME desktop. -
How did you install distrobox?
From the OpenSUSE repos.
Additional context
- As per https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/283, I initially had this problem even outside the distrobox. It was resolved by adding my user to the "render" group. Therefore this is most likely a permissions issue related to the
/dev/dri/render*
nodes. - Curiously,
glxinfo
can see my GPU inside the distrobox so it seems to be an issue that only affects Vulkan and not OpenGL.