mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #5967] Docker-in-Docker not working with Colima on macOS M-series #1305
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#1305
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 @eirisdg on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/5967
Bug report info
Command used with act
Describe issue
I'm running act on macOS with an M-series chip (Apple Silicon) using Colima as the Docker provider. When executing workflows that require Docker-in-Docker capabilities (actions that run docker run commands inside the workflow), the Docker socket is not accessible within the container.
Current Behavior:
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?What Works:
What Doesn't Work:
Root Cause: The --container-daemon-socket flag doesn't seem to properly mount the Colima socket inside the container, or there's an issue with how Colima sockets are handled compared to Docker Desktop on macOS.
Expected behavior
When using --container-daemon-socket with Colima on macOS M-series chips, the Docker socket should be mounted inside the container at /var/run/docker.sock, allowing GitHub Actions to execute Docker commands (Docker-in-Docker).
This should work similarly to how it works with Docker Desktop or when using -P arc-runners=-self-hosted.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@ChristopherHX commented on GitHub (Nov 11, 2025):
Set env
DOCKER_HOST=unix:///Users/adominguez/.colima/docker.sockThen
--container-daemon-socket "/Users/adominguez/.colima/docker.sock"needs to be changed to the socket path inside the colima VM. However idk what path is needed, because I am not a colima user.Podman Desktop has a much easier way, just enable Docker Compatibility using admin rights and act works out of box.