config VS rpm-ostree-toolbox

https://github.com/ublue-os/config/blob/main/build/ublue-os-...

There's a default `distrobox` with pytorch in ublue-os/config//build/ublue-os-just/etc-distrobox/apps.ini:

flatpak-system-update.timer.flatpak list | grep Steam ) If it's the flatpak you likely need to run flatpak update -y to get NVidia drivers that match your system. Otherwise you might fall back to software rendering. This command will have to be re-run every time you update your NVidia drivers (After just about every dnf upgrade command). You can have it run automatically with systemd units, see here. (Thanks to the ublue.it team for that btw! ) Just copy those two files into /etc/systemd/system, and run sudo systemctl daemon-reload && sudo systemctl enable

We include a bunch of extra udev rules for controllers and other hardware: That container is here specifically if you want to inspect it: https://github.com/ublue-os/config

For the isobuilder, I would really suggest that you use the long-form Lorax builder above (the templates are in their repo) rather than mkksiso. This seems like added complexity for no reason, but outside of sucking bandwidth that you're paying for every time someone fetches it from cloudfront, the way it's currently done more or else forces anyone who downloads the ISO to re-fetch the compose, and use more bandwidth, or just outright fail in airgapped environment, and it's sure to make your CI (if you have CI around the ISO) much slower than it needs to besides.