mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2579] RUNNER_ARCH and -self-hosted #1175
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1175
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @derrik-fleming on GitHub (Dec 18, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2579
Bug report info
Command used with act
Describe issue
Seems like the
--container-architectureflag has no effect with-self-hosted.I understand the name doesn't really make sense given that it's not running in a container when using the
-self-hostedflag, so I'm not surprised that it doesn't work in the same way it would when running in a container. But I am making use of an Action in my Workflow that depends on the architecture, and whenRUNNER_ARCHis set to the defaultamd64the Action fails.I'm looking for a way to be able set
RUNNER_ARCHwhen using-self-hosted. I've tried setting it via--envand on my system, in both cases it seems like it gets overridden by Act.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@ChristopherHX commented on GitHub (Dec 18, 2024):
Make a PR to map amd64 to x64?
Here is the code:
github.com/nektos/act@9c7f103bb3/pkg/container/host_environment.go (L426)go buildif it works fork this repo and make a Pullrequest@derrik-fleming commented on GitHub (Dec 18, 2024):
Happy to do so. Is there a case where
amd64is useful and the map you described would be undesirable?I assumed
amd64was the default for a reason, but it wasn't immediately obvious to me why.@ChristopherHX commented on GitHub (Dec 19, 2024):
I don't think such a case exist for act (for my
github-act-runnerthis is a breaking change to document), all actions should expectX64github-act-runnerhad used the raw values for all of them, but as usage in this upstream repo increased for officially supported platforms it has been requested to use the same values if they are documented.