-
Notifications
You must be signed in to change notification settings - Fork 204
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
cdi generate
cannot find config files in non-standard locations
#475
Comments
Hi @elezar Thanks for the pointer here #82 (comment) Apologies, I hand't realised it was added in the end. When I went back and checked the chagne logs, I noticed that there were two mentioned ways added to find config files:
I tried However, just to clear up the mystery of the differences between the two search options. Are they looking for different types of config files, and I'm misunderstanding the intention, or should they work largely the same and find the same config files ? Here is the debug log of the attempt to use
Thanks! |
Hi,
When generating CDI config, if the json config files for
glvnd
, vulkanor
egl` are not in a "standard" location, the are not found. It fails as below:It's possible to specify alternate search paths for libraries via
--library-search-path
. It would be awesome to be able to do the same for config file paths. This was discussed a bit over in #82, specifically #82 (comment) , but it didn't make it into release as there were some issues testing it at the time and there was no pressing need for the config files then either. I have now found some use cases for adding the config files via CDI, and it would be great to be able to do that.I'm testing this for use in the docker snap packaging, where the non-kernel driver artefacts are in non-standard locations on Ubuntu Core systems. This should further expand the uses that can leverage nvidia hardware via docker.
Currently running latest toolkit version,
v1.15.0
If you need any further logs or info, please let me know.
FYI @elezar
Thank you.
The text was updated successfully, but these errors were encountered: