-
Notifications
You must be signed in to change notification settings - Fork 207
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
why does nvidia-container-cli load libnvidia-ml via dlopen rather than linking directly? #223
Comments
What OS did you build on and what packages did you install? |
I did the compile on an ubuntu-based system, but I plan on using it on Alpine as well as possibly a custom-composed OS, so possibly no package manager. |
I think this might be a larger-scale issue actually: since NVidia distributes most of the drivers and libraries in the binary form, most of those also only come linked against glibc? E.g. the cuda libraries, except for some chosen jetson platforms?
I'm not sure this would work in case of
Unlike |
Actually, the Jetson platform (the "official OS", anyways) is glibc-based.
How interesting.
What do you mean? |
Why does nvidia-container-cli load libnvidia-ml via dlopen rather than linking directly? It uses
dlopen()
, so it has to find it in the path. This creates a few issues:ldd
does not tell me of the dependencies, nor does compiling from source indicate that I will need itIf I am running other than a pre-installed OS with that package, I am stuck. And there are lots of custom OS builds there, or versions of an OS, etc.
Separately, if I did want to install it, how do I get it for other OSes, e.g. musl-based like Alpine? Or build from source? I managed to get everything in this repo built from source, including on Alpine, but it fails on run because of that
libnvidia-ml
dependency.The text was updated successfully, but these errors were encountered: