Default to Bazel target architecture

[Paul Draper]

🚀 feature request

Relevant Rules

container_image

Description

The target architecture is always transitioned. By default it transitions to amd64.

The sensible behavior is to use the current target architecture. It's weird that it doesn't, and rules_docker seems to have gone out of its way(?) to make it like that.

Describe the solution you'd like

--

Describe alternatives you've considered

Disable rules_docker transitions and do it myself.

[Thomas]

It should transition to the target architecture of the image, given:

rules_docker/container/image.bzl

Lines 805 to 811 in 8e70c6b

 "@io_bazel_rules_docker//platforms:image_transition_cpu": "@platforms//cpu:" + { 
     # Architecture aliases. 
     "386": "x86_32", 
     "amd64": "x86_64", 
     "ppc64le": "ppc", 
 }.get(attr.architecture, attr.architecture), 
 "@io_bazel_rules_docker//platforms:image_transition_os": "@platforms//os:" + attr.operating_system, 

[Paul Draper]

Right, and my point is that the architecture of the image should default to the Bazel target platform (--cpu).

Currently, it defaults to amd64

rules_docker/container/image.bzl

Line 578 in 8e70c6b

 default = "amd64",