mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #1658] Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? on macOS while docker commands are working #822
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#822
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 @LenaWil on GitHub (Mar 2, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1658
Bug report info
Command used with act
Describe issue
I expected it to not print
Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?, because commands likedocker psdo work:Link to GitHub repository
github.com/LenaWil/Squire@d038cc03cdWorkflow content
Relevant log output
Additional information
(On a repo with GitHub workflow actions, this one:
github.com/LenaWil/Squire@d038cc03cd)There are more workflows, and looking at the debug log it might run some of them? But without verbose mode it prints two error messages.
@culshaw commented on GitHub (Mar 2, 2023):
I don't think this is necessarily an act specific problem, but I've got around this by doing the following:
This isn't guaranteed to fix your problem long-term. However it looks like an upgrade to a
v4.17.0of docker for mac has meant docker has moved away from using this global .sock file@LenaWil commented on GitHub (Mar 2, 2023):
That worked, thanks!
@mingrammer commented on GitHub (Mar 3, 2023):
Thank you @culshaw.
@pvmtriet232 commented on GitHub (Apr 16, 2023):
I got into the problem too. I use ubuntu, how can I solve it?
@bernardoforcillo commented on GitHub (Apr 18, 2023):
So do I (fedora)
@kintel commented on GitHub (Apr 19, 2023):
I also have this failure on Ubuntu-22.04:
The user running this is added to the
dockergroup and can run docker commands without sudo.@catthehacker commented on GitHub (Apr 19, 2023):
Original issue was regarding Docker on macOS, if you have similar problem on non macOS platform, create new issue and attach required info.
@kintel commented on GitHub (Apr 19, 2023):
See #1744
@LenaWil commented on GitHub (Apr 19, 2023):
Why was this closed? Last time I tested I still had the issue.
I can use the work around, but for some reason I have to do that on every boot.
@jpdrsn commented on GitHub (Apr 21, 2023):
Using rancher desktop and getting the same issue. Solution was similar to @LenaWil suggestion:
sudo ln -s ~/.rd/docker.sock /var/run/docker.sock@gentildpinto commented on GitHub (Apr 28, 2023):
I've docker desktop on my Fedora, so I do
sudo ln -s ~/.docker/desktop/docker.sock /var/run/docker.sock. And it worksThanks ❤️
@palerdot commented on GitHub (Sep 13, 2024):
I'm using
colimaand following works@jakeseg commented on GitHub (Nov 8, 2024):
I can not run build docker images on my local worflows anymore.
I followed instrctions from:
https://github.com/docker/actions-toolkit/issues/250#issuecomment-2427084411
https://github.com/nektos/act/issues/2239
Inside the workflow I was not able to connect to the
docker.socketbut after creating the simlink (sudo ln -s~/.colima/default/docker.sock /var/run/docker.sock) and using--container-daemon-socket=unix:///var/run/docker.sockit said Permision denied.I'm little dissapointed dact stoped working, I have no clue how to fix it. I know the issue is related to a docker change and mac OS update.
@jeiksegovia commented on GitHub (Nov 9, 2024):
solved the issue on my machine 🥹 https://github.com/nektos/act/issues/2239#issuecomment-2466020469
@mcloughlan commented on GitHub (Dec 3, 2024):
For those still having the issue. Check the following
/var/run/docker.sockand that it points to another file that should exist in~/.docker/run/docker.sock~/.actrcdoes not override the container socket path to-or an invalid location with the--container-daemon-socketargument. (this was my issue)@matheusbsi1992 commented on GitHub (Feb 24, 2025):
In docker: https://docs.docker.com/engine/install/ubuntu/#set-up-the-repository. Using help from long upgrade.
@mmaryo commented on GitHub (May 27, 2025):
same problem by default with ubuntu