mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #5946] Why is there no documentation on using act under MacOS? #1294
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#1294
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 @iloving on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/5946
Bug report info
Command used with act
Describe issue
Act is made available on Mac, but there is zero documentation on how to actually use it. I'm also using Rancher Desktop rather than Docker Desktop. Between the two, I am completely unable to use act whatsoever.
It detects what sockets are available, and still manages to ignore them unless I set DOCKER_HOST. When I set DOCKER_HOST, it still can't connect. I created a symlink to /var/run/docker.sock. It still can't connect. Sudo? Nope.
I was finally able to somehow make it work using VS Code, with the github local actions extension. But to do it, I had to:
act --container-architecture linux/amd64 -P linux=-self-hostedDOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') codeIt is completely unreasonable to force people to have to struggle through just basic usage, and have to spend hours or days googling, trying to find the choice tidbit of information they need to make it work.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
After much trial and error, I got VS Code Github Local Actions extension executing by configuring the Act Command setting to 'act --container-architecture linux/amd64 -P linux=-self-hosted' but I still can't get past the docker socket problem.
@panekj commented on GitHub (Oct 8, 2025):
https://nektosact.com/missing_functionality/docker_context.html
@ChristopherHX commented on GitHub (Oct 8, 2025):
Literally for me
YMMV
In my opinion, this is common in open source projects. People do not get paid for such improvements.