Closed sikhness closed 1 month ago
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
I think passing through /dev/dri
is not enough. Look at the official guide to get VA-API inside the container:
@onomatopellan thank you so much, that was it!
I felt like I scoured the entire internet but wasn't able to find that, wished all this was documented on Microsoft's website instead of having to scrape through various Github issues/commits & blog posts.
Windows Version
Microsoft Windows [Version 10.0.22631.3880]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
vainfo --display drm
and all supported profiles for the video card should be published/dev/dri
usingsudo docker run -it --privileged --name ubuntu --device /dev/dri:/dev/dri:rwm ubuntu:22.04 bash
apt update; apt install vainfo -y
andexport LIBVA_DRIVER_NAME=d3d12
vainfo --display drm
within the Docker containerExpected Behavior
I expected vainfo within the container to output the same information as the WSL2 host which is the following:
Actual Behavior
Instead what I got was a
resource allocation failed
error and I'm unable to use the/dev/dri
device as shown below in the container output ofvainfo --display drm
:Diagnostic Logs
No response