mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2314] act not respecting --container-daemon-socket argument #1072
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#1072
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 @bretdavi89 on GitHub (May 2, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2314
Bug report info
Command used with act
Describe issue
When passing docker socket on the command line, it gets ignored, and default is used instead.
If set via DOCKER_HOST environment variable, then it is picked up correctly.
I tested this with version 0.2.59 and that one works as expected, and the correct socket is used.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@bretdavi89 commented on GitHub (May 2, 2024):
Actually just noticing that in newer version, it's treating docker host/socket separately:
Using docker host 'unix:///var/run/docker.sock', and daemon socket 'unix:///run/user/1000/docker.sock'So it is picking up the socket, but still trying to use the default one as well?
On the older version, simply passing the socket via the command line worked properly. Not sure why there are 2 variables for this
@webjay commented on GitHub (Sep 4, 2024):
Same in act version 0.2.66
@github-actions[bot] commented on GitHub (Mar 4, 2025):
Issue is stale and will be closed in 14 days unless there is new activity