mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #917] Issue: failed to run docker containers as steps #546
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#546
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 @KnisterPeter on GitHub (Dec 8, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/917
Originally assigned to: @catthehacker on GitHub.
System information
act: node:12-buster-slimactversion: LatestmasterExpected behaviour
This workflow should output the node.js version installed in the alpine container:
Actual behaviour
This is the panic log:
@github-actions[bot] commented on GitHub (Jan 8, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@vkhodygo commented on GitHub (Jan 12, 2022):
I have a suspicion I experience the same problem.
I use Arch with the following
dockerinstalled:I tried to build a
.pdfdocument, and it looks to me that I fail at the samecontext needs => map[]step:@github-actions[bot] commented on GitHub (Feb 13, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@JJRcop commented on GitHub (Feb 19, 2022):
Still an issue
@josephgardner commented on GitHub (Mar 21, 2022):
Is there a workaround for this?
Edit: I got past this by installing node in the container as part of the workflow.
@carlthome commented on GitHub (Mar 23, 2022):
Still an issue. I think this would only be a matter of mounting the
--container-daemon-socketspecified Docker daemon socket to thedocker createcommand per job so the jobs can use the host's Docker.