Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-detection of ARM runner fails #61

Closed
wearebasti opened this issue Jul 19, 2023 · 1 comment · Fixed by #65
Closed

Auto-detection of ARM runner fails #61

wearebasti opened this issue Jul 19, 2023 · 1 comment · Fixed by #65

Comments

@wearebasti
Copy link

wearebasti commented Jul 19, 2023

We tried running a couple of our jobs on the ARM instances of buildjet, everything works fine on the x64 based ones.

We use the auto-detect feature in this action, but it stops after detecting the OS:

Run jaxxstorm/action-install-gh-release@v1.10.0
  with:
    repo: cloudflare/cloudflared
    extension-matching: disable
    rename-to: cloudflared
    chmod: 755
    token: ***
    tag: latest
  env:
    AWS_DEFAULT_REGION: eu-central-1
    AWS_REGION: eu-central-1
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
    AWS_SESSION_TOKEN: ***
==> System reported platform: linux
==> Using platform: linux

So in the next step(s) we are faced with a /home/runner/actions-runner/_work/_temp/485aef00-6518-476f-858a-831665b49bc3.sh: line 14: cloudflared: command not found

We were trying to run on the actions-runner image buildjet-2vcpu-ubuntu-2204-arm. It works fine on the non-arm based buildjet-2vcpu-ubuntu-2204

Is there something we're missing to have the detection work on ARM as well?

@jaxxstorm
Copy link
Owner

The action uses the arch detection from the standard os package in nodejs:

import * as os from "os";

osArch = os.arch()

If the detection is failing on buildjet, it's an issue with node os module. I'd start with just running os.arch() and go from there.

If the os.arch() works outside this action, please let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants