mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2459] AZ_CLI_GITHUB_ACTION_1726245395565.sh: No such file or directory%0A #1132
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#1132
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 @AndreRicardo-Zoetis on GitHub (Sep 13, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2459
Bug report info
Command used with act
Describe issue
Rather than having the version of
az versiongot the errorAZ_CLI_GITHUB_ACTION_1726245395565.sh: No such file or directory%0A.Confirmed on GitHub that the workflow works fine
https://github.com/AndreRicardo-Zoetis/act-issue/actions/runs/10852886032/job/30119932094
Link to GitHub repository
https://github.com/AndreRicardo-Zoetis/act-issue
Workflow content
Relevant log output
Additional information
No response
@AndreRicardo-Zoetis commented on GitHub (Sep 13, 2024):
Same issue with latest version of act
@ChristopherHX commented on GitHub (Sep 13, 2024):
Please try
-P ubuntu-latest=-self-hosted(this means get rid of the job container that doesn't exist by default on GitHub Hosted Runners)Actions managing their own containers and using bind mounts usually don't work in default job conainers due to environmental differences.
@merlinz01 commented on GitHub (Jan 29, 2025):
I'm getting the same error.
@chibidev commented on GitHub (Mar 20, 2025):
This will not help OP, but may help others facing the same issue.
Encountered the same on macOS using OrbStack as container engine. Turns out that when the azure/cli action spins up the
mcr.microsoft.com/azure-clicontainer, it maps the directory stored in the variable$RUNNER_TEMP, which is/tmpby default. The container engine sees/tmp, but instead of mapping from the act executor container, it maps from the host itself.The action creates a temporary script at
$RUNNER_TEMP(which is why it tries to bind mount it).So @ChristopherHX was spot on, but unfortunately adding
-P ubuntu-latest=-self-hostedis not a feasible solution, because the action requires linux-based OS as runner. Adding--container-options "-v /tmp:/tmp"to theactcommand invocation was the correct solution in my case.