config VS ostree

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

Not a tanget at all! https://gitlab.com/fedora/ostree/ci-test/ is the current location of the composed images we derive from.

That's what ends up on quay.io/fedora-ostree-desktops/ which is what we use to make our base images.

Fedora is in the middle of a transition to make more official images on quay.io/fedora, I'm sorry I don't have the info offhand, it's probably in here somewhere: https://discussion.fedoraproject.org/tag/silverblue/l/top?pe...

It takes about 40 minutes to build an image that way vs 2 minutes to derive your own, so for us it's easier to build from the existing base images that Fedora provides: https://gitlab.com/fedora/ostree/ci-test - it makes sense for Fedora to build it this way (hyperreal, the vauxite author was able to submit they're work into this repo, which is nice!)