I am not sure whether this qualifies as a BUG or is just a misconfiguration on my part, anyways i am glad for any help/information.
I am running the container on a system with Intel iGPU AND Intel dedicated GPU (arc 370m).
Upon pulling and starting the container everything worked, but the dedicated GPU was not used.
On such systems, applications can be forced to use the dedicated GPU by setting the env var DRI_PRIME=1.
I added this variable to my .config/zwift (maybe this should automatically set by the script? I am unsure whether it causes any side effects) but this lead to zwift not starting.
The docker logs revealed: failed to open /dev/dri/renderD129: Permission denied
I tried (and error-ed) a lot to give the container permissions to access the device, but the only thing that worked was to chmod 666 the device, which I'd really rather avoid.
The question is, is anyone aware of how those permissions can be granted and can this be incorporated into the script?
For reference:
I found some similiar issues (e.g. this or hints to the group-add flag ), all those were either not better to my solution or didn't work.
ls -l /dev/dri total 0 drwxr-xr-x 2 root root 120 Oct 15 21:06 by-path crw-rw----+ 1 root video 226, 0 Oct 15 21:06 card0 crw-rw----+ 1 root video 226, 1 Oct 15 19:15 card1 crw-rw----+ 1 root render 226, 128 Oct 15 19:15 renderD128 crw-rw----+ 1 root render 226, 129 Oct 15 21:06 renderD129
I am not sure whether this qualifies as a BUG or is just a misconfiguration on my part, anyways i am glad for any help/information.
I am running the container on a system with Intel iGPU AND Intel dedicated GPU (arc 370m).
Upon pulling and starting the container everything worked, but the dedicated GPU was not used.
On such systems, applications can be forced to use the dedicated GPU by setting the env var DRI_PRIME=1.
I added this variable to my .config/zwift (maybe this should automatically set by the script? I am unsure whether it causes any side effects) but this lead to zwift not starting.
The docker logs revealed:
failed to open /dev/dri/renderD129: Permission deniedI tried (and error-ed) a lot to give the container permissions to access the device, but the only thing that worked was to
chmod 666the device, which I'd really rather avoid.The question is, is anyone aware of how those permissions can be granted and can this be incorporated into the script?
For reference:
I found some similiar issues (e.g. this or hints to the
group-addflag ), all those were either not better to my solution or didn't work.ls -l /dev/dri total 0 drwxr-xr-x 2 root root 120 Oct 15 21:06 by-path crw-rw----+ 1 root video 226, 0 Oct 15 21:06 card0 crw-rw----+ 1 root video 226, 1 Oct 15 19:15 card1 crw-rw----+ 1 root render 226, 128 Oct 15 19:15 renderD128 crw-rw----+ 1 root render 226, 129 Oct 15 21:06 renderD129