Skip to content

fix(compose): support Docker Desktop WSL2 NVIDIA workflow - #3973

Draft
karttikjangid wants to merge 1 commit into
JdeRobot:humble-develfrom
karttikjangid:feat/verify-windows
Draft

fix(compose): support Docker Desktop WSL2 NVIDIA workflow#3973
karttikjangid wants to merge 1 commit into
JdeRobot:humble-develfrom
karttikjangid:feat/verify-windows

Conversation

@karttikjangid

Copy link
Copy Markdown
Contributor

Summary

This PR updates the Windows-specific NVIDIA Docker Compose configurations to
support Docker Desktop with WSL2.

Problem

The existing Windows NVIDIA Compose configuration attempts to expose /dev/dri.
That device is not available in the WSL2 GPU environment used by Docker Desktop,
where the GPU is exposed through the WSL2 graphics stack instead.

This causes the container to fail before the RoboticsAcademy application starts.

Changes

  • Updated compose_cfg/dev_humble_nvidia_windows.yaml.
  • Updated compose_cfg/user_humble_nvidia_windows.yaml.
  • Removed the /dev/dri device mapping from the Windows-specific NVIDIA
    configurations only.
  • Corrected the duplicate environment definition in the Windows user
    configuration so the YAML has a single effective environment block.
  • Kept the Linux and other platform Compose configurations unchanged.

Validation

Tested on Windows 11 with Docker Desktop and WSL2:

  • Docker Compose stack starts without the /dev/dri device error.
  • NVIDIA GPU is visible inside the container.
  • WSL2 GPU rendering was verified through the D3D12/Mesa path.
  • The RoboticsAcademy container starts successfully.

Scope

This PR is limited to the Docker Desktop + WSL2 Windows workflow.

It does not modify RoboticsApplicationManager, exercise code, or the Linux
Docker workflow.

- LD_LIBRARY_PATH=/usr/lib/wsl/lib
devices:
- /dev/dri
- PYTHONPATH=/RoboticsApplicationManager

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be needed as it has worked before without it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants