mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2222] Composite action with docker action in a reusable workflow fails #1050
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#1050
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 @nnyiri on GitHub (Feb 15, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2222
Bug report info
Command used with act
Describe issue
I have a composite action which uses another action(appleboy/ssh-action@v1.0.0), which creates a container.
I can use it inside a reusable workflow (deploy)
But if I call the workflow from another workflow, the container creation fails.
It work altough if it is run by github
The structure is the following:
Workflow "main" runs on push and call the reusable WF "deploy".
WF "deploy" calls the composite action.
The composite action has a step where a container will be created
The test action:
Link to GitHub repository
https://github.com/atlas-it-gmbh/test-realm
Workflow content
WF Deploy
Additional information
No response
@TechnicallyJoe commented on GitHub (Jun 12, 2024):
We are experiencing a similar issue. Not sure what's causing it.
@github-actions[bot] commented on GitHub (Dec 10, 2024):
Issue is stale and will be closed in 14 days unless there is new activity
@stopthatastronaut commented on GitHub (Dec 18, 2024):
We seem to be experiencing a similar issue, workflow in repo A calls out to a reusable workflow in repo B. That workflow is composite, in that it calls out to other workflows within repo B
Fails with an error "no such file or directory" but the path in the error points to repo A, not repo B where the workflow exists.
I could maybe try fully-qualified paths in the composite repo, but these are fairly widely used within our org, so there may be impacts. Anyway, it appears to be a departure from github's own behaviour in this scenario.
@stopthatastronaut commented on GitHub (Dec 18, 2024):
I suspect the problem is in how
actdetermines what's local or remote inworkflow.goinType()I might be able to work round by using a fully-qualified path or by tapping a
@on the end of the reference. I'll have to work up a repro though, can't fiddle with the live one