Netlify-cli 23.15.1 installs AMD deno binary on ARM

Start with the Edge Functions setup flow referenced in dist/lib/edge-functions/proxy.js, especially prepareServer, and inspect how the Deno binary is selected for Linux arm64. Reproduce the failure in an arm64 container; done means Netlify CLI downloads and runs the arm64 Deno binary instead of the AMD binary.

Describe the bug

✖ Setting up the Edge Functions environment. This may take a couple of minutes.
 ›   Error: Netlify CLI has terminated unexpectedly
This is a problem with the Netlify CLI, not with your application.
If you recently updated the CLI, consider reverting to an older version by running:

npm install -g netlify-cli@VERSION

You can use any version from https://ntl.fyi/cli-versions.

Please report this problem at https://ntl.fyi/cli-error including the error details below.

Error: Failed to set up Deno for Edge Functions.
Error: Command failed with exit code 255: /root/.config/netlify/deno-cli/deno --version
qemu-x86_64-static: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
Downloaded to: /root/.config/netlify/deno-cli/deno
Platform: linux/arm64

This may be caused by permissions, antivirus software, or platform incompatibility.

Try clearing the Deno cache directory and retrying:
  /root/.config/netlify/deno-cli

Supported Deno versions: ^2.4.2

To install Deno manually: https://ntl.fyi/install-deno
    at toError (file:///usr/local/share/nvm/versions/node/v24.13.1/lib/node_modules/netlify-cli/dist/utils/command-helpers.js:143:16)
    at logAndThrowError (file:///usr/local/share/nvm/versions/node/v24.13.1/lib/node_modules/netlify-cli/dist/utils/command-helpers.js:149:17)
    at prepareServer (file:///usr/local/share/nvm/versions/node/v24.13.1/lib/node_modules/netlify-cli/dist/lib/edge-functions/proxy.js:150:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async Promise.all (index 1)
    at async file:///usr/local/share/nvm/versions/node/v24.13.1/lib/node_modules/netlify-cli/dist/lib/edge-functions/proxy.js:72:41
    at async onRequest (file:///usr/local/share/nvm/versions/node/v24.13.1/lib/node_modules/netlify-cli/dist/utils/proxy.js:608:35)

  System:
    OS: Linux 6.17 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (5) arm64 unknown
  Binaries:
    Node: 24.13.1 - /usr/local/share/nvm/versions/node/v24.13.1/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 11.8.0 - /usr/local/share/nvm/versions/node/v24.13.1/bin/npm
  npmGlobalPackages:
    netlify-cli: 23.15.1

Steps to reproduce

I trust that the above is explicit enough. For what it's worth, I faced this error while trying to run netlify in a VS Code Dev Container using podman on a Mac M1 with the following:
netlify dev -c 'bundle exec jekyll serve --livereload --incremental'

Workaround

For now, I've worked around the problem by doing a simple npm install -g deno before running netlify. This installs the following version which works just fine:

$ deno --version
deno 2.6.8 (stable, release, aarch64-unknown-linux-gnu)
v8 14.5.201.2-rusty
typescript 5.9.2

Configuration

[build]
base = "docs/"
publish = "_site/" # relative to base directory
command = "bundle exec jekyll build"

[context.deploy-preview]
command = "bundle exec jekyll build --drafts --future"

Environment

$ npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli
Need to install the following packages:
envinfo@7.21.0
Ok to proceed? (y)

System:
OS: Linux 6.17 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (5) arm64 unknown
Memory: 1.93 GB / 3.53 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 24.13.1 - /usr/local/share/nvm/versions/node/v24.13.1/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 11.8.0 - /usr/local/share/nvm/versions/node/v24.13.1/bin/npm
pnpm: 10.29.3 - /usr/local/share/nvm/versions/node/v24.13.1/bin/pnpm
Deno: 2.6.8 - /usr/local/share/nvm/versions/node/v24.13.1/bin/deno
npmGlobalPackages:
netlify-cli: 23.15.1