break containers compatibility about libnvidia-container HOT 8 CLOSED

The error is coming from your container image, not the CLI.
We have OpenGL images available. If you do not wish to use them, you will need to replicate what they do.

The fact that it works after deleting the CLI suggest that Singularity does something that it shouldn't do and you got lucky.

from libnvidia-container.

What is your question? It's not clear from the issue description

from libnvidia-container.

show this Issues with singularity

the list generated with nvidia-container-cli is incomplete.

from libnvidia-container.

The list is correct. Anything else should be provided by the container (e.g. official container images).
Singularity doesn't always use the CLI which is why you see different behaviors.

from libnvidia-container.

I apologize for reopening the issue, I tried to isolate any error factor, so do not use any official image of nvidia, I'm working on the official image of "centos: latest Docker" and do not install drivers on the other hand. So I do not know exactly what the problem is, the only way I found to solve it is the method that I mentioned. After deleting CLI, I have no problem with opengl.

from libnvidia-container.

You want nvidia/opengl:1.1-glvnd-runtime-centos7 or nvidia/opengl:1.1-glvnd-devel-centos7

from libnvidia-container.

Nice to know that you have official OpenGL images available. I guess that OpenGL libraries are not strictly tied to the kernel module so it is not necessary to bind them in from the host? Do I understand correctly @3XX0?

from libnvidia-container.

@GodloveD yes, thanks to libglvnd.

from libnvidia-container.