You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a bug, just a question to understand what I am doing.
I use the GPU operator to deploy OpenGL applications in a Kubernetes Cluster. It works fine, my pod (a basic glxgears) starts and when running nvidia-smi from the nvidia-driver pod I can see that glxgears is using the GPU (and the metrics are consistent with the usage of hardware acceleration).
However, when looking within the container some things are unclear.
When I inspect the content of the container on my PC, ie without the GPU Operator, I can see that the installation of glx-utils package comes with some default openGL libraries (with mesa implementation) :
[root@9417bac3962a lib64]# ls -al /usr/lib64/ |grep libGL
lrwxrwxrwx 1 root root 14 Nov 11 2022 libGL.so.1 -> libGL.so.1.7.0
-rwxr-xr-x 1 root root 558944 Nov 11 2022 libGL.so.1.7.0
lrwxrwxrwx 1 root root 15 Nov 11 2022 libGLX.so.0 -> libGLX.so.0.0.0
-rwxr-xr-x 1 root root 141256 Nov 11 2022 libGLX.so.0.0.0
lrwxrwxrwx 1 root root 20 Nov 11 2022 libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0
-rwxr-xr-x 1 root root 502032 Nov 11 2022 libGLX_mesa.so.0.0.0
lrwxrwxrwx 1 root root 27 Nov 11 2022 libGLX_system.so.0 -> /usr/lib64/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 22 Nov 11 2022 libGLdispatch.so.0 -> libGLdispatch.so.0.0.0
-rwxr-xr-x 1 root root 769048 Nov 11 2022 libGLdispatch.so.0.0.0
When running the same command within the container deployed in my cluster with the GPU Operator i have the following result :
We can also see that the application is not linked with the libraries built with my version of the driver.
The configuration of my X-Server is pretty the same as it is started in another pod and I noticed exactly the same thing.
So my question is pretty basic : how can this work ? It seems that my application loads the mesa version of the libGL, libGLX & libGLdispatch, however the display is well rendered by the GPU. Am I missing something ? It would be great if I can find deep documentation of these mechanisms.
If necessary, I'm using the following versions :
GPU Operator : 23.6.1
Container toolkit : 1.13.4-ubuntu20.04
Thanks!
Regards,
The text was updated successfully, but these errors were encountered:
Hello,
This is not a bug, just a question to understand what I am doing.
I use the GPU operator to deploy OpenGL applications in a Kubernetes Cluster. It works fine, my pod (a basic glxgears) starts and when running
nvidia-smi
from the nvidia-driver pod I can see that glxgears is using the GPU (and the metrics are consistent with the usage of hardware acceleration).However, when looking within the container some things are unclear.
When I inspect the content of the container on my PC, ie without the GPU Operator, I can see that the installation of glx-utils package comes with some default openGL libraries (with mesa implementation) :
When running the same command within the container deployed in my cluster with the GPU Operator i have the following result :
First observations :
If now I have a look to libraries present in the same container but in the volume shared with the host where libraries are installed :
We can notice that for the following libraries :
The version present in
/usr/lib64
is the one initially installed in the container and not the one mounted by the nvidia stack.When looking to an extract of the links of the application :
We can also see that the application is not linked with the libraries built with my version of the driver.
The configuration of my X-Server is pretty the same as it is started in another pod and I noticed exactly the same thing.
So my question is pretty basic : how can this work ? It seems that my application loads the mesa version of the libGL, libGLX & libGLdispatch, however the display is well rendered by the GPU. Am I missing something ? It would be great if I can find deep documentation of these mechanisms.
If necessary, I'm using the following versions :
Thanks!
Regards,
The text was updated successfully, but these errors were encountered: