| Does bootc-image-builder build Native Containers? Do Native Containers work as VM images that can be stored in an OCI Image/Artifact/Package Registry? I've been mentioning Native Containers since I realized that was how bazzite works now. Is vagrant necessary anymore if host, vm, and container images can all be signed and stored in an OCI Image store? From https://news.ycombinator.com/item?id=44137501 re: Firecracker and Microsandbox VMs : > ostree native containers are bootable host images that can also be built and signed with a SLSA provenance attestation; https://coreos.github.io/rpm-ostree/container/ ublue-os/image-template: https://github.com/ublue-os/image-template : > Build your own custom Universal Blue Image ublue-os/akmods has nvidia GPU drivers, nvidia-open, zfs: https://github.com/ublue-os/akmods : > A caching layer for pre-built Fedora akmod RPMs > OCI images providing a set of cached kernel RPMs and extra kernel modules to Universal Blue images. Used for better hardware support and consistent build process. nvidia-container-toolkit (CDI) is necessary for --gpus=all to do CUDA and libEGL 3D with podman. Is this also already installed in bazzite? ublue-os/toolboxes: "quadlets and systemd service units for management", boxkit :
https://github.com/ublue-os/toolboxes#images ublue-os/devcontainer .devcontainer/devcontainer.json:
https://github.com/ublue-os/devcontainer/blob/main/src/base/... It looks like the Just Justfile 40-nvidia.just has moved due to image topology simplification? https://news.ycombinator.com/item?id=39364975 : > ublue-os/config//build/ublue-os-just/40-nvidia.just defines the `ujust configure-nvidia` and `ujust toggle-nvk` commands |