11–20 of 34 posts
Earlier quoted context omitted.
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?
You'd think so:) Unfortunately the current implementation hardcodes calls to dnf: https://github.com/osbuild/bootc-image-builder/issues/869
You 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
Can this do vmdk format?
I've used this to start from a minimal base and added what I've needed on top. Best of all, updates are delivered via a container registry.
> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
Does anyone have experience worth sharing with both?
What I like about this is always having a known working image I can quickly swap to, particularly for the machine with an nvidia card.
I've always been hesitant to use this method over debootstrap: the Ubuntu container images ("FROM ubuntu:20.04") are created from a tarball that Ubuntu's convoluted CI system spits out and I'm not confident I understand if it's somehow suitable only for a container and not for real hardware.
We also have a GUI for trying this out! https://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!