Skip to content

image: Make a VM's aliases as incompatible as the VM - #341

Merged
daandemeyer merged 2 commits into
amutable-systems:mainfrom
daandemeyer:push-rxwpnvzrspwu
Oct 20, 2026
Merged

daandemeyer merged 2 commits into
amutable-systems:mainfrom
daandemeyer:push-rxwpnvzrspwu

Conversation

@daandemeyer

Copy link
Copy Markdown
Member

image_vm and vm_smoke only boot a disk of the host's architecture, so they
require the host's cpu. Their distribution aliases don't. Buck reports a
compatible alias over an incompatible VM as an error, so a build of tine//...
for another architecture can't skip the aliases. Let's give every distributed
rule a target_compatible_with that adds to the distributions it serves and
that its aliases take as well.

Signed-off-by: Daan De Meyer daan@amutable.com

The pinned buck2 reports a target whose target_compatible_with resolves to
select_incompatible() as an error instead of skipping it. A target that can't
be built for an architecture then needs a constraint value that no platform
sets. The 2026-10-20 release contains the upstream fix, so let's bump to it.

Signed-off-by: Daan De Meyer <daan@amutable.com>
Comment thread docs/user/images.md Outdated
Comment thread docs/user/images.md Outdated
image_vm and vm_smoke only boot a disk of the host's architecture, so they
require the host's cpu. Their distribution aliases don't. Buck reports a
compatible alias over an incompatible VM as an error, so a build of tine//...
for another architecture can't skip the aliases. Let's give every distributed
rule a target_compatible_with that adds to the distributions it serves and
that its aliases take as well.

Signed-off-by: Daan De Meyer <daan@amutable.com>
@daandemeyer
daandemeyer merged commit 22a76a1 into amutable-systems:main Oct 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants