mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2508] container Jobs Fail #1160
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#1160
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 @afrazkhan on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2508
Bug report info
Command used with act
Describe issue
Initially, I got the error:
After some searching around, I started running act with
--container-daemon-socket -, which got past this problem. Unfortunately, it sees to have caused another problem which is that jobs usingcontainerhave all of their steps run in the specified container image.For example in this workflow:
the steps "Checkout code" and "Zip up the Lambdas" run fine, but the "Archive artifacts" step fails because
nodeis unavailable in theghcr.io/guidionops/terraform-cloud-deployer:0.1.2image. All of these steps work fine in Github Actions, since theactions/upload-artifact@v4action does not try to run in the container above.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@red-avalanche commented on GitHub (Feb 27, 2025):
Duplicate of https://github.com/nektos/act/issues/973