-
Notifications
You must be signed in to change notification settings - Fork 202
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
Support for openSUSE Tumbleweed #110
Comments
Wish I could provide some help but I am suffering from the same problem. Wish I could tell zypper to replace the dependency libseccomp2 by libseccomp since it is what provides the package libseccomp Have a great day! And thank you! |
@kilian-hu @pmrj33 would creating a dummy For example: nvidia-container-toolkit/test/release/docker/centos8/Dockerfile Lines 13 to 25 in 6094eff
One could also use |
I ended up building the package nvidia-container-toolkit (repo) from github with target opensuse-leap15.1-x86_64 and creating a local repo for nvidia-container-toolkit to install on the system and to zypper to handle. I only just installed and didn't yield any errors. Also run on podman this simple example |
@pmrj33 note that only the Another note: If you're only looking to use CDI (which your example suggests), then only the |
Alright, very good point. I am kind of learning how to use podman/docker + nvidia and the exact terms definition. Indeed I see I bypassed the problem with an extreme solution. But when it was building the packages I noticed it fetched libseccomp2 instead of libseccomp, that why I got away with it. Again thank you for your help. And I had done the build before read your post @elezar and thank you for the solution |
Thank you very much for the help @elezar :) |
This seems un-fixed. Is there a solution other than installing a dummy package? |
Hi all. I am working on a solution that involves adding a virtual package that provides Would this be workable? |
@elezar any idea when your solution will be available? |
I found out that when installing package Only
Speaking of which, one has to wonder why that However once I got the
|
@bubbleguuum thanks for your latest reply. With regards to:
This is unexpected. I assume that this is a legacy change that has made it into this package and was never an issue until we started rolling out our "unified" packages. I think we can definitely drop the With regards to:
What does:
output on your system? |
@rajinder-yadav if we can get consensus that this is a reasonable workaround (as opposed to force-installing the |
Default output of
Notice that there is no |
Thanks for the feedback @bubbleguuum. The logic added to detect a SUSE-based system for the generation of the default config was not working correctly. I have created https://gitlab.com/nvidia/container-toolkit/container-toolkit/-/merge_requests/532 to address this. |
Hello I can confirm the fix made by @elezar is working, thank you. 🙏 |
Hi,
I'm using openSUSE Tumbleweed and tried to follow the installation guide with zypper but encountered this error:
Problem: nothing provides 'libseccomp' needed by the to be installed nvidia-container-toolkit-1.14.1-1.x86_64
.I found that in openSUSE Tumbleweed the package is actually called
libseccomp2
. Would it be possible to adjust the repo such that the installation on openSUSE Tumbleweed works? Any help is highly appreciated :)The text was updated successfully, but these errors were encountered: