SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: how open nvidia gpu and webgl application?
Open
Nobody has claimed this yet.
R-awaiting-answer
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
The gpu graphics device cannot be recognized?
Command used to start Selenium Grid with Docker (or Kubernetes)
docker run -d --gpus all -e SE_VNC_NO_PASSWORD=true -e SE_BROWSER_ARGS_CUSTOM2="--disable-gpu-sandbox" -e SE_BROWSER_ARGS_CUSTOM5="--ignore-gpu-blocklist" -e SE_BROWSER_ARGS_CUSTOM6="--enable-gpu-rasterization" -e SE_BROWSER_ARGS_CUSTOM7="--enable-webgl" -e SE_BROWSER_ARGS_CUSTOM8="--disable-software-rasterizer" -e SE_BROWSER_ARGS_CUSTOM9="--use-gl=desktop" -e SE_BROWSER_ARGS_CUSTOM9="--enable-features=VaapiVideoDecoder" -e SE_BROWSER_ARGS_CUSTOM9="--disable-dev-shm-usage" -e SE_BROWSER_ARGS_CUSTOM10="--enable-unsafe-webgpu" -e SE_BROWSER_ARGS_CUSTOM11="--enable-features=Vulkan,WebGPU" -p 4444:4444 -p 7900:7900 --shm-size="8g" selenium/standalone-chrome:latest
Relevant log output
Platform: Linux x86_64
Browser User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36
Context Name: webgl2
GL Version: WebGL 2.0 (OpenGL ES 3.0 Chromium)
Shading Language Version: WebGL GLSL ES 3.00 (OpenGL ES GLSL ES 3.0 Chromium)
Vendor: WebKit
Renderer: WebKit WebGL
Unmasked Vendor: Google Inc. (Mesa)
Unmasked Renderer: ANGLE (Mesa, llvmpipe (LLVM 19.1.1 256 bits), OpenGL 4.5)
Antialiasing: Available
ANGLE: No
Major Performance Caveat: No
Operating System
windows11 docker-desktop
Docker Selenium version (image tag)
latest
Selenium Grid chart version (chart version)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the selenium/standalone-chrome:latest command on Windows 11 with Docker Desktop, then compare the reported WebGL renderer and GPU detection logs. Done means establishing whether the NVIDIA GPU can be recognized instead of the logged Mesa llvmpipe renderer, with a reproducible configuration or a documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100