Problem
The official tutorial "Linux option 2: Run qli-Client as Linux Service (Expert)"
instructs users to download the install script from:
https://dl.qubic.li/cloud-init/qli-Service-install-auto.sh
The script hardcodes the x64 package:
package=qli-Client-3.8.4-Linux-x64.tar.gz
There is no architecture detection (e.g. uname -m), so on ARM64 Linux machines
the script downloads the x64 client, which cannot run. Every user who follows
the official guide on ARM64 hardware hits this wall immediately.
This is unnecessary: official Linux ARM64 packages have existed since 3.8.3
(e.g. qli-Client-3.8.5-Linux-arm64.tar.gz is available on dl.qubic.li).
Suggested fix
Detect the architecture automatically:
ARCH=$(uname -m)
case "$ARCH" in
x86_64) package=qli-Client-3.8.5-Linux-x64.tar.gz ;;
aarch64) package=qli-Client-3.8.5-Linux-arm64.tar.gz ;;
*) echo "Unsupported architecture: $ARCH"; exit 1 ;;
esac
Related
Discovered while debugging #136 (Linux ARM64 worker distribution bug).
Problem
The official tutorial "Linux option 2: Run qli-Client as Linux Service (Expert)"
instructs users to download the install script from:
The script hardcodes the x64 package:
There is no architecture detection (e.g.
uname -m), so on ARM64 Linux machinesthe script downloads the x64 client, which cannot run. Every user who follows
the official guide on ARM64 hardware hits this wall immediately.
This is unnecessary: official Linux ARM64 packages have existed since 3.8.3
(e.g.
qli-Client-3.8.5-Linux-arm64.tar.gzis available ondl.qubic.li).Suggested fix
Detect the architecture automatically:
Related
Discovered while debugging #136 (Linux ARM64 worker distribution bug).