arm32v6 not downloaded with get-cli.sh
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by reading the get-cli.sh installer referenced in the issue and trace how it detects and maps the armv6l architecture. Reproduce the detection on an arm32v6 system or with an equivalent test; done means the installer downloads pangolin-cli_linux_arm32v6 rather than pangolin-cli_linux_arm32.
Written by the indexing model from the issue text.
Description
Describe the Bug
I tried to use the cli on a Raspberry pi zero with arm32v6.
I used the install instructions and used https://static.pangolin.net/get-cli.sh but it is downloading the v7 version.
pi@pizero-a01:~ $ curl -fsSL https://static.pangolin.net/get-cli.sh | sudo bash
[INFO] Installing latest version of Pangolin...
[INFO] Fetching latest version...
[INFO] Latest version: v0.18.1
[INFO] Detected platform: linux_arm32
[INFO] Found existing Pangolin binary at /usr/local/bin/pangolin
[INFO] Will update existing installation at /usr/local/bin
[INFO] Install directory: /usr/local/bin
[INFO] Downloading Pangolin from https://github.com/fosrl/cli/releases/download/0.18.1/pangolin-cli_linux_arm32
[INFO] Pangolin installed to /usr/local/bin/pangolin
[INFO] Installation successful!
[INFO] pangolin version: unknown
[INFO] Pangolin is ready to use!
pi@pizero-a01:/usr/local/bin $ uname -m
armv6l
pi@pizero-a01:/usr/local/bin $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Environment
- OS Type & Version: (e.g., Ubuntu 22.04)
- Pangolin Version:
- Gerbil Version:
- Traefik Version:
- Newt Version:
- Client Version: (if applicable)
To Reproduce
Use the setup script curl -fsSL https://static.pangolin.net/get-cli.sh | bash on an arm32v6 system.
AI Disclosure
No AI used
Expected Behavior
v6 version https://github.com/fosrl/cli/releases/download/0.18.1/pangolin-cli_linux_arm32v6 will be downloaded instead of v7 https://github.com/fosrl/cli/releases/download/0.18.1/pangolin-cli_linux_arm32
- Dominant language
- Go
- Stars
- 58
- Forks
- 19
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 11
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fosrl/cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
CLI on Windows not able to switch org (and account)May be free again @oschwartz10612 claimed this 68 days ago, and no pull request is open. Openbug
fosrl/cli#121 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Error messages are sent to stdout, not to stderrPossibly taken @marcschaeferger claimed this 139 days ago. Openneeds investigating
fosrl/cli#74 · 4 comments · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Fix the nix packageOpengood first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 28/100
Maintainers usually reply within 1 day
Similar issues
-
L: github:actions L: php:composer
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dependabot/dependabot-core#16493 ·
Maintainers usually reply within 1 day
-
Controller pods on default limits CrashLoopBackOff and constantly reclaim memoryPossibly taken @brsmnv claimed this today. Openbug
Difficulty 2/5 Under an hour Newbie friendliness 68/100
ironcore-dev/ironcore-net#560 ·
Maintainers usually reply within 1 day
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead countsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/registry#1692 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mark3labs/mcp-go#1039 · 1 comment ·
Maintainers usually reply within 8 days