bazzite

s the best, tomorrow they will see the price of this smoothness and it will turn into another Ventoy-style drama[3]. [1] https://github.com/ublue-os/bazzite/blob/ad5704b87388fbde7e3... [2] https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0... [3] https://github.com/ventoy/Ventoy/issues/2795

regularly use is fish shell, and the updates are so few and far between (and very public) I think the risk is low. I suppose this isn't strictly a container-specific problem; you could add the repos and install / update all those packages yourself too. But being able to package everything up into a single file that you can then boot into as your OS means you're also packing all the supply chain risk. Curious if anyone else shares my concern or if I should just put my tinfoil hat back on... 1. https://github.com/ublue-os/bazzite/blob/main/Containerfile 2. https://github.com/ublue-os/bazzite/releases/tag/42.20250417

rfile#... has, in addition to fan and power controls, automatic updates on desktop, supergfxctl, system76-scheduler, and an fsync kernel: rpm-ostree install rocm-hip \ rocm-opencl \ rocm-clinfo But it's not `rpm-ostree install --apply-live` because its a Containerfile. To install a ublue-os distro, you install any of the Fedora ostree distros: {Silverblue, Kinoite, Sway Atomic, or Budgie Atomic} from e.g. a USB stick and then `rpm-ostree rebase <OCI_host_image_url>`: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:stable rpm-ostree rebase ostree-image-signed: ublue-os/config//build/ublue-os-just/40-nvidia.just defines the `ujust configure-nvidia` and `ujust toggle-nvk` commands: 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: https://github.com/ublue-os/config/blob/main/build/ublue-os-... [mlbox] image=nvcr.io/nvidia/pytorch:23.08-py3 additional_packages="nano git htop" init_hooks="pip3 install huggingface_hub tokenizers transformers accelerate datasets wandb peft bitsandbytes fastcore fastprogress watermark torchmetrics deepspeed" pre-init-hooks="/init_script.sh" nvidia=true pull=true root=false replace=false docker.io/rocm/pytorch: https://hub.docker.com/r/rocm/pytorch pytorch/builder//manywheel/Dockerfile: https://github.com/pytorch/builder/blob/main/manywheel/Docke... ROCm/pytorch//Dockerfile: https://github.com/ROCm/pytorch/blob/main/Dockerfile The ublue-os (and so also bazzite) OCI host image Containerfile has Sunshine installed; which is a 4k HDR 120fps remote desktop solution for gaming. There's a `ujust remove-sunshine` command in system_files/desktop/shared/usr/share/ublue-os/just/80-bazzite.just : https://github.com/ublue-os/bazzite/blob/main/system_files/d... and also kernel args for AMD: pstate-force-enable: rpm-ostree kargs --append-if-missing=amd_pstate=active ublue-os/config//Containerfile: https://github.com/ublue-os/config/blob/main/Containerfile LizardByte/Sunshine: https://github.com/LizardByte/Sunshine moonlight-stream https://github.com/moonlight-stream Anyways, hopefully this PR fixes the immediate issue: https://github.com/invoke-ai/InvokeAI/pull/5714/files conda-forge/pytorch-cpu-feedstock > "Add ROCm variant?": https://github.com/conda-forge/pytorch-cpu-feedstock/issues/... And Fedora supports OCI containers as host images and also podman container images with just systemd to respawn one or a pod of containers.