exec /__e/node20/bin/node: no such file or directory

on:
  pull_request:
    types: [opened, synchronize]

name: Tag Created

jobs:
  tag-created:
    runs-on: rtx4090-1
    container:
      image: nvcr.io/nvidia/l4t-tensorrt:r8.0.1-runtime

    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: v0.2.0
...

I am trying to do cross-compilation. The self-hosted runner is x86-64, but the Docker image is arm64. However, I am encountering the following error.

Run actions/checkout@v4
  with:
    ref: v0.[2](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:2).0
    repository: TechWhiskers/fastflow_core
    token: ***
    ssh-strict: true
    persist-credentials: true
    clean: true
    sparse-checkout-cone-mode: true
    fetch-depth: 1
    fetch-tags: false
    show-progress: true
    lfs: false
    submodules: false
    set-safe-directory: true
/usr/bin/docker exec  0[3](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:3)0cae08918d43e6cbb15a[4](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:4)a5b7b1b192276fc6a65970291c246d34a8349c3a0 sh -c "cat /etc/*release | grep ^ID"
exec /__e/node20/bin/node: no such file or directory

Does the GitHub runner support this method?

Start by tracing container-job execution around the /usr/bin/docker exec invocation and actions/checkout@v4's /__e/node20/bin/node entry point. Reproduce the arm64 image on the x86-64 self-hosted runner and compare the runner's container architecture handling; done means establishing whether this configuration is supported and documenting the resulting behavior.