container_image rules don't take into account the architecture of underlying container_import

[dastbe]

🐞 bug report

Affected Rule

container_image, but also the associated language rules

Is this a regression?

In some sense yes, as pre-transition rules you could control this centrally

Description

With the implementation of image transition logic, it's now the case that the architecture/operating system of the container_image rule are used to transition build configuration to build for that image. However, two primary problems

1. most lang rules don't even support wiring this through, so regardless of what you want it will default to amd64/linux
2. there's no guarantee that the underlying container_import's arch/os are aligned with the container_image's output arch/os

so while the image transition rules are really good for "ensure the image is built for amd64/linux", they're detrimental to actually building for any other platform.

🔬 Minimal Reproduction

TODO

🔥 Exception or Error

🌍 Your Environment

Operating System:

  
macos, linux
  

Output of bazel version:

  
4.2.3, but not dependent
  

Rules_docker version:

  
0.23
  

Anything else relevant?

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

[github-actions]

This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"