[Bug]: The python added to my rules_oci image is matching the machine architecture where bazel executed instead of the machine architecture of my rules_oci image

[blockjon-dd]

What happened?

I'm creating a multi-architecture OCI image which contains both an arm64 (aka aarch64) image and also one for x86_64 (also known as amd64).

When I run my container on an x86_64/amd64 machine, the problem is that my py_binary errors like this:

qemu-aarch64: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory

How can I have rules_py ensure that the python architecture that gets added to my rules_oci images matches the architecture of the oci image?

Version

Development (host) and target OS/architectures:

Output of bazel --version: bazel 7.2.1

bazel_dep(name = "rules_python", version = "0.32.2") bazel_dep(name = "aspect_bazel_lib", version = "2.7.7") bazel_dep(name = "aspect_rules_py", version = "0.7.3")

How to reproduce

No response

Any other information?

No response