bootc

ectory, Copies dependency files into the build context, Runs the container build using Podman or Docker How to Use Ansible to Build Podman Images > Building with Build Arguments, Multi-Stage Builds, Building with Buildah: https://oneuptime.com/#building-with-buildah : It's possible to build images using build a commands in an ansible playbook: buildah from buildah copy buildah run buildah config buildah commit . The CLI way to traverse an ansible playbook graph, for e.g. dagger: ansible-playbook --list-tags ansible-playbook --tags {tagname} But where can it parallelize? It probably shouldn't (?) parallelize because that wouldn't be a deterministic build; installing A then B is not the same as installing B then A. (Is not the same thing as installing A in one container image layer, B in another container image layer, and then trying to merge the package databases.) A given package B could conditionally install or configure according to whether or not A is already installed, and so for example package install tasks are not commutative. . Bootc (osbuild) builds VM and native machine images from Containerfiles: bootc-image-builder bootc upgrade /? bootc ansible [Debian] https://www.google.com/search?q=bootc+ansible https://www.google.com/search?q=bootc+ansible+debian "Demonstrate a debian or arch base image" bootc-dev/bootc#865 https://github.com/bootc-dev/bootc/issues/865 Is packer necessary with bootc? To require signatures for containers and also for native containers with bootc: cat /etc/containers/policy.json | grep sigstoreSigned podman image trust show --raw Here's this on ansible, dagger, bootc: "Public link: Dagger for Programmable CI/CD" https://gemini.google.com/share/3965633a3ff8

id even on Bazzite). Now onto the post specifically: LTS from a CentOS Stream base seems interesting. Fedora is nice, and the universalblue team tames it 99%, but its edge can be a bit too bleeding sometimes. My only reticence with CentOS Stream though is that it is veering dangerously close to Red Hat proper which I am unsure how to feel about. I am eagerly awaiting when non-rpms distros will be able to use the same underlying technology Bluefin uses, and see how the space evolves. A debian base especially seems interesting in theory. There has recently been some progress on that front: https://github.com/bootc-dev/bootc/issues/865 https://github.com/bootcrew/debian-bootc

wikipedia.org/wiki/Virt-manager) if desired. In short though, secureblue and Qubes aren't really analogous. We have different goals and target use cases. There is even an open issue on Qubes to add a template to use secureblue as a guest: https://github.com/QubesOS/qubes-issues/issues/9755

work and doesn't work how to reproduce it (because currently someone even trying to see what the current state of things looks like has to navigate through several layers of pages and can still walk away uncertain). My vague plan is [x] try building a qcow2 image from quay.io/centos-bootc/centos-bootc:stream9 [x] try building a lightly modified container image from centos stream and turn that into a qcow2 [ ] try building frap129's archlinux image [ ] write up minimal steps to reproduce frap129's archlinux image and boot it in qemu [ ] try building a debian image [ ] try building an alpine image [ ] try building a postmarketos image (my actual original goal) and either leave a trail of documentation of how to do things that do work, or else write up exactly what breaks.

d/issues/468 , which is 2 years old and... basically is, again, a bunch of different folks saying they'd like to make it work on different distros and getting nowhere. There is one person who posted on https://github.com/bootc-dev/bootc/issues/865 and who claims to have converted an ostree Arch system to using bootc, but they didn't post steps to reproduce. Actually clicking around I eventually found their repo https://github.com/frap129/arch-bootc/tree/main which again doesn't say how to do it, but does appear to contain their code, so maybe I can reverse-engineer from there... Anyways. The community would very much like to step up, but we can only step up over so high of a learning curve, or possibly so high of a porting curve (a lot of comments indicate being tied to rpm integration).

ple previous ones (which are otherwise unconnected). I think Earthly can parallelize this scenario https://earthly.dev/