bootc-image-builder: Build your entire OS from a Containerfile
1–10 of 34 posts
Re: bootc-image-builder: Build your entire OS from a Containerfile
#2https://github.com/podman-desktop/extension-bootc
We’re also starting to see other projects adopt a “OS as a Container image” such as Bazzite: https://bazzite.gg/ using bootc :)
Feel free to ask any questions!
Re: bootc-image-builder: Build your entire OS from a Containerfile
#3> nix-build '' -A vm -I nixpkgs=channel:nixos-25.05 -I nixos-config=./configuration.nix
I use nixos btw
Re: bootc-image-builder: Build your entire OS from a Containerfile
#4...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
Re: bootc-image-builder: Build your entire OS from a Containerfile
#5Do 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
Re: bootc-image-builder: Build your entire OS from a Containerfile
#6Re: bootc-image-builder: Build your entire OS from a Containerfile
#7You can also achieve this with your current system > nix-build ' ' -A vm -I nixpkgs=channel:nixos-25.05 -I nixos-config=./configuration.nix I use nixos btw
Re: bootc-image-builder: Build your entire OS from a Containerfile
#8Does 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…
Re: bootc-image-builder: Build your entire OS from a Containerfile
#9> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
Re: bootc-image-builder: Build your entire OS from a Containerfile
#10> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
Is there something about this makes it red hat specific. An OS is just a specific collection of files in the end. Whether things are installed with rpm or Deb shouldn't matter?