Comment by westurner
8 months ago
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 > 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/toolboxes#images ublue-os/devcontainer .devcontainer/devcontainer.json:
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
What does "native containers" mean in this context?
> ostree native containers are bootable host images that can also be built and signed with a SLSA provenance attestation
From https://coreos.github.io/rpm-ostree/container/#ostree-native... :
> rpm-ostree inherits work in ostree-rs-ext to create “container native ostree” functionality. This elevates OCI/docker containers to be natively supported as a transport mechanism for bootable operating systems.
I think it means simplification of complexity and unnecessary re-duplication.