Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VirtualGL torch issue #69

Open
muratmaga opened this issue Dec 9, 2024 · 0 comments
Open

VirtualGL torch issue #69

muratmaga opened this issue Dec 9, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@muratmaga
Copy link
Contributor

This is a known issue. When an application is started with virtuaGL then torch fails to locate the cudnn library and fails. This impacts all torch based modules in Slicer. See the posts on VGL repo:

VirtualGL/virtualgl#227
VirtualGL/virtualgl#209

Note that this is independent on the of the NVIDIA driver related torch problem reported here #66. I have replicated the current issue with 550 series non grid driver on a vanilla exosphere g3.xl instance.

Since the Slicer shortcut in MorphoCloud is indeed configured to use vgl, it means applications that rely on torch fails. To avoid confusion about when to invoke Slicer with or without vgl, I propose we stop using vgl and try the native accelerated X recipe provided by the JetStream documentation

@muratmaga muratmaga added the enhancement New feature or request label Dec 9, 2024
@muratmaga muratmaga added this to the Release 1.1 milestone Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants