swa deploy seems to get stuck on arm64 #974
Description
Are you accessing the CLI from the default port :4280 ?
- No, I am using a different port number (
--port) and accessing the CLI from that port - Yes, I am accessing the CLI from port
:4280 - I am not using any port
Describe the bug
swa deploy seems to get stuck on arm64
To Reproduce
Steps to reproduce the behaviour:
- Be on a arm64 system
- Type in command 'npx swa deploy ...'
- See application stuck somewhere after
Fetching release metadata for version: stable. Please wait...
GET https://aka.ms/swalocaldeploy
Decode JSON: <Removed for brevity>
Local client binary is up to date. Skipping download.
Deploying using /root/.swa/deploy/53b7d0e07fe5c34bf68929fab92f87ce910288dc/StaticSitesClient@53b7d0e07fe5c34bf68929fab92f87ce910288dc
Deploying using the following options:
- env: <removed for brevity>
(Same thing works on a x86-64 system)
Expected behavior
Ideally: swa deploy works on arm64
Better than nothing: swa deploy exits with an error on arm64
System
- Azure VM "Standard D4pds v6"
- Docker container based on
node:24 - OS:
Debian GNU/Linux 12 (bookworm) - npm:
11.5.1 - node:
v24.7.0 - swa:
2.0.6
Additional context
When manually starting StaticSitesClient, it reports ./StaticSitesClient: cannot execute binary file: Exec format error
file ./StaticSitesClient reports ./StaticSitesClient: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=2c1e53af795f334d83be915591e65fee55966751, stripped