`distrobox create name example nvidia
distrobox create --name example-nvidia-toolkit --additional-flags "--runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=all -e NVIDIA_DRIVER_CAPABILITIES=all" --image nvidia/cuda
Adidn't seem to work, this is the full command line:
Afails with:
me thinks this is because of the
me thinks this is because of the
--user root:rootAin podman by default your user maps to root so therefore no permission issues
Adistrobox uses
--userns keep-id and --user root:root which means your user maps to itself and root maps to rootAworks if you use
distrobox with --root
Bchange the
/etc/nvidia-container-runtime/config.toml to remove no-cgroups = true ?Bah
A
AI think at least for bazzite this should work ok, just add the stuff in the assemble file
Keugh, does it have to be root?
Kthat's unfortunate
Kand distrobox is going to start enforcing root containers having their own passwords
Kwhich means I can't just assemble them
Kunless I also pass a flag to disable password checks at all, which is very dangerous
Anot really, it works on rootless podman
Ait just that distrobox combination of flags makes it using that flag is the lowest-effort workaround
Amm this probably means it will incompatible with toolbox images, at least semantically as toolbox images require
I guess the effect is that any password won't do anything when using these images as
:NOPASSWD on sudo anywayI guess the effect is that any password won't do anything when using these images as
sudo will just not ask anywayK
Kat least this might solve the controller issue
Bthe issue where it has to be connected before the container starts?
Kyea
Bnice!
AThat affects flatpak too I think, we need a udev event proxy 
Kso what exactly is needed to get this working then? I'm down to make some test images
AFor the nvidia thing?
KYeah, saw something about generating a file and deleting an existing one
KJust making sure I have all the pieces since I can't test this myself
KUnless that's upstream already
AYou just need to use the latest version of the nvidia container toolkit
AAnd generate the CDI file
KAh cool, that's easy 
ACDI configuration is hardware specific
KThat CDI is optional, no? I saw something about being able to skip it and generate on the fly
Kvia nvidia.com/all as an arg
ANo I think that just selects all gpus
AI didn’t try on the new container toolkit version though because ublue is outdated in that part
KNvidia's docs say that CDI can change from driver updates
KSo unless we're generating that often that may be a problem
KLet me find what I was reading just in case we can avoid this
Bi should get that updated today sometime, so tomorrow's builds should have newer toolit
K
AI guess that works
AUnclear what the difference is
B nothing like bypassing merge protectionhttps://github.com/ublue-os/akmods/commit/45719c8d4f2320772f8a4584c70a3b715fbfd88b
GitHub
This enables us to get a newer nvidia container toolkit version 1.14
which now provides root and rootless podman modes without configuration
files, plus CDI.
Added some links to docs.
which now provides root and rootless podman modes without configuration
files, plus CDI.
Added some links to docs.
