Building x86_64-v2 instead of x86_64-v3
Hi all, hi @Luke Skywunker !
For my https://eu-os.eu project, I switched to AlmaLinux packages. They build by default for arch = amd64v3. On old hardware (think of schools), this does not run anylonger. Also not on my Thinkpad x220 test device. A PR is open to build the bootc image for amd64v2 as well. https://github.com/AlmaLinux/atomic-desktop/pull/38
It seems to me that bluebuild does not expose the --arch flag from podman, so I do not see how I could force bluebuild to pick one x86_64 over the other (unless I build on a device with only v2 support).
Closest issue so far is https://github.com/blue-build/cli/issues/340 on multi-arch. For the time being, one specific arch would be good for me.
For my https://eu-os.eu project, I switched to AlmaLinux packages. They build by default for arch = amd64v3. On old hardware (think of schools), this does not run anylonger. Also not on my Thinkpad x220 test device. A PR is open to build the bootc image for amd64v2 as well. https://github.com/AlmaLinux/atomic-desktop/pull/38
It seems to me that bluebuild does not expose the --arch flag from podman, so I do not see how I could force bluebuild to pick one x86_64 over the other (unless I build on a device with only v2 support).
Closest issue so far is https://github.com/blue-build/cli/issues/340 on multi-arch. For the time being, one specific arch would be good for me.
GitHub
For example as in this upstream: being able to publish multiarch images, something like: image-version: 41 default-arch: amd64 arch: amd64,aarch64
