The 0.1.6 release included a linux-arm binary, the 0.2.1 release only includes a linux-arm64 binary. On arm32, the install script still tries to download the linux-arm binary, which fails with a HTTP 404 error.
Possibly related to #27, but the workaround of just downloading the arm64 binary does not work on a system that is actually arm32.
However, if I modify the install script to download 0.2.1 instead of the latest release, it seems to work without issue.
The ideal fix would be providing arm32 binaries of the latest version again.
If not supporting arm32 is intentional, it should be documented somewhere. You might also consider providing a script that just installs the legacy 0.2.1 release, so that users do not have to modify the install script themselves.
The 0.1.6 release included a
linux-armbinary, the 0.2.1 release only includes alinux-arm64binary. On arm32, the install script still tries to download the linux-arm binary, which fails with a HTTP 404 error.Possibly related to #27, but the workaround of just downloading the arm64 binary does not work on a system that is actually arm32.
However, if I modify the install script to download 0.2.1 instead of the latest release, it seems to work without issue.
The ideal fix would be providing arm32 binaries of the latest version again.
If not supporting arm32 is intentional, it should be documented somewhere. You might also consider providing a script that just installs the legacy 0.2.1 release, so that users do not have to modify the install script themselves.