Feel free to reject this change - this is simply a hunch.
I changed [fedora] in /etc/distrobox/distrobox.ini to use ublue-os/fedora-toolbox:latest instead of ublue-os/fedora-distrobox:latest.
On one hand, ujust distrobox-assemble fedora pulls from ublue-os/fedora-distrobox:latest.
On the other hand, the fedora-distrobox-quadlet.container in toolboxes repo pulls from ublue-os/fedora-toolbox:latest.
I assume intended UX is that ujust distrobox-assemble fedora also enables quadlet functionality.
Context
I have used bluefin-dx-nvidia for a while but have largely stuck to vanilla silverblue workflows until today, where I have been reading through the documentation and learning the intended workflows.
I was investigating why the "default key bindings" for Ptyxis was not working for me, and learned about quadlets, which I believe my system does not have set up, as ~/.config/containers/systemd did not exist.
Change summary
Feel free to reject this change - this is simply a hunch.
I changed [fedora] in
/etc/distrobox/distrobox.ini
to useublue-os/fedora-toolbox:latest
instead ofublue-os/fedora-distrobox:latest
.ujust distrobox-assemble fedora
pulls fromublue-os/fedora-distrobox:latest
.fedora-distrobox-quadlet.container
intoolboxes
repo pulls fromublue-os/fedora-toolbox:latest
.ujust distrobox-assemble fedora
also enables quadlet functionality.Context
I have used
bluefin-dx-nvidia
for a while but have largely stuck to vanilla silverblue workflows until today, where I have been reading through the documentation and learning the intended workflows.I was investigating why the "default key bindings" for Ptyxis was not working for me, and learned about quadlets, which I believe my system does not have set up, as
~/.config/containers/systemd
did not exist.Details
rpm-ostree status -v