mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #1798] Linux support for access to docker.socket #878
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#878
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 @andrew-pickin-epi on GitHub (May 10, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1798
Act version
0.2.45-10
Feature description
Unless by some chance the gid of docker group on host machine and runner image coincide the docker.socket will give permissions denied error when attempting to run docker build or similar command.
There are ways round this,
chown 1001 /var/run/docker.sockchmod a+rw /var/run/docker.sockBut these might conflict with other needs, not survive a reboot.
It should be possible to read the
gidof/var/run/docker.sockon startup and add this value to the invocation of the runner image. (Seedocker run --group-add).@fabiobsantosprogrow commented on GitHub (Feb 2, 2024):
Got the same error today!
After searching one hour on issues and stack overflow found this post.
I have the same issue when using docker compose too but docker-compose was a optional as dependency.
@alexjball commented on GitHub (Apr 2, 2024):
In my setup,
chownandchmoding the docker socket changes permissions on both the host and container, breaking docker on my host.Instead, I was able to use
--container-optionsto pass in--group-addto workflow containers, which does the trick:@mahula commented on GitHub (May 6, 2024):
Thank you, that solved the docker access issue.
@jonathanlinat commented on GitHub (Jun 21, 2024):
It still does not work, unfortunately.
Update
It worked using the following command instead:
@piotrpdev commented on GitHub (Jun 23, 2025):
Did you try this?