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

Fix for mrview / singularity / NVIDIA #2559

Merged
merged 2 commits into from
Nov 24, 2024

Conversation

celstark
Copy link
Contributor

Simple addition to the documentation. Without the "--nv" flag, Singularity doesn't pass through the required access to NVIDIA drivers. If you're not using these, the existing code should work. But, if you do have NVIDIA drivers installed, you need to tell Singularity to get access to them.

@Lestropie Lestropie added bug gui container Docker or Singularity containers documentation labels Jan 10, 2023
@Lestropie
Copy link
Member

Lestropie commented Jan 11, 2023

It might take a little more effort to sort out exactly how to refine the documentation (and potentially container recipes also) to try to get the containers not only working with mrview, but using manufacturer device drivers when doing so. (Frankly I was content at the time to get it working with something better than software rendering and no terminal warnings or errors...)

Currently the only Linux system I have access to is a laptop with dual GPU (Intel integrated + NVidia) and I have had multiple failed attempts to get Optimus working. I had a go with 3.0.4 and got the following:

When building image using Singularity recipe:

singularity run -B /run MRtrix_3.0.4_fromsingularity.sif mrview
(runs, but uses Intel GPU)

singularity run -B /run --nv MRtrix_3.0.4_fromsingularity.sif mrview
INFO:    underlay of /usr/bin/nvidia-smi required more than 50 (398) bind mounts
mrview: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /.singularity.d/libs/libGLdispatch.so.0)
mrview: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /.singularity.d/libs/libGLX.so.0)

When building Singularity image from dockerhub:

singularity run -B /run MRtrix_3.0.4_fromdockerhub.sif mrview
dbus[35071]: D-Bus library appears to be incorrectly set up: see the manual page for dbus-uuidgen to correct this issue. (Failed to open "/var/lib/dbus/machine-id": No such file or directory; Failed to open "/etc/machine-id": No such file or directory)
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)

I'd rather confirm on a non-Optimus system before committing to changes. I'll also have another go at Optimus on this system...

@Lestropie Lestropie added this to the 3.0.5 updates milestone Sep 16, 2024
@bjeurissen bjeurissen enabled auto-merge November 20, 2024 09:49
@bjeurissen bjeurissen added this pull request to the merge queue Nov 24, 2024
Merged via the queue into MRtrix3:master with commit c9bdac0 Nov 24, 2024
5 checks passed
@Lestropie Lestropie mentioned this pull request Jan 14, 2025
31 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug container Docker or Singularity containers documentation gui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants