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.
GitHub
feat: multiarch recipes/images/tags · Issue #340 · blue-build/cli
For example as in this upstream: being able to publish multiarch images, something like: image-version: 41 default-arch: amd64 arch: amd64,aarch64
5 Replies
Almalinux now has a v2 variant:
Things I tried:
In recipe.yml:
base-image: --variant=v2 quay.io/almalinuxorg/atomic-desktop-kde
I also tried to set the sha256, but this did not work either.
Gives same error as above.I'll have to add this in as a platform
Got a change to add more platforms https://github.com/blue-build/cli/pull/501
GitHub
feat: Add all linux platforms by gmpinder · Pull Request #501 · b...
This add support for building images for all platforms that are supported by podman and docker. This will be the pre-cursor to adding support for specifying platforms to build in the recipe and clo...
@Luke Skywunker Is selecting a particular image by sha256 already supported?
Yeah, it just requires the right syntax
I put that in the issue