I understand that the bootc / anaconda approach is outside of the current scope for the autosd-image-builder.
However, I still find this approach useful for the "safe high performance" use case in the railway domain. Both the rolling stock and the trackside infrastructure are using x86_64 architecture hardware. These rack mounted boards are not exactly what I would call embedded systems.
Meanwhile I was able to create a containers.bootc ostree.bootable image from the automotive-image-builder ostree-commit export:
sudo ./auto-image-builder.sh build --target pc --dist autosd --export ostree-commit --define use_composefs=false --define use_autoinit=false --define use_composefs_signed=false images/developer.aib.yml autosd.commit rpm-ostree compose container-encapsulate --repo=./autosd.commit autosd9/x86_64/pc-developer docker://quay.io/shetze/autosd:dev-reg-x86-001
After some trial and error, I am able to use this image to rebase my anaconda-iso installation of the quay.io/centos-bootc/centos-bootc:stream9 The trickiest part was to find the right partitioning for the centos-bootc installation with uuid and labels fitting the local-fs.target requirements for autosd.
bootfs_uuid: 156f0420-627b-4151-ae6f-fda298097515 # Hic sunt dracones ;-)