starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #219] Job is not ran using runner user #152

New issue

Closed

opened 2026-03-01 21:40:41 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 21:40:41 +03:00

Owner

Originally created by @kenorb on GitHub (May 2, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/219

When running job locally, the action is run using root, on GitHub workflow, it's runner user:

uid=1001(runner) gid=116(docker) groups=116(docker)

This difference can affect the job results.

Originally created by @kenorb on GitHub (May 2, 2020). Original GitHub issue: https://github.com/nektos/act/issues/219 When running job locally, the action is run using `root`, on GitHub workflow, it's `runner` user: > `uid=1001(runner) gid=116(docker) groups=116(docker)` This difference can affect the job results.

kerem

2026-03-01 21:40:41 +03:00

closed this issue
added the
stale

area/action

kind/bug
labels

kerem commented

2026-03-01 21:40:42 +03:00

Author

Owner

@tobernguyen commented on GitHub (Jun 4, 2020):

Yes I'm experiencing some permission issues when running a global npm command like yo. yo doesn't have permission to create/modify files in github workspace.

@tobernguyen commented on GitHub (Jun 4, 2020): Yes I'm experiencing some permission issues when running a global npm command like `yo`. `yo` doesn't have permission to create/modify files in github workspace.

kerem commented

2026-03-01 21:40:42 +03:00

Author

Owner

@tobernguyen commented on GitHub (Jun 4, 2020):

Yes I'm experiencing some permission issues when running a global npm command like yo. yo doesn't have permission to create/modify files in github workspace.

I just found that the problem I'm having is because when act copy working directory from local to the container (via checkout@v2 action), it doesn't chmod the dirs/files to correct owners (user and group), it just keep filers/folders' ownership the same with what is in local.

@tobernguyen commented on GitHub (Jun 4, 2020): > Yes I'm experiencing some permission issues when running a global npm command like `yo`. `yo` doesn't have permission to create/modify files in github workspace. I just found that the problem I'm having is because when act copy working directory from local to the container (via checkout@v2 action), it doesn't chmod the dirs/files to correct owners (user and group), it just keep filers/folders' ownership the same with what is in local.

kerem commented

2026-03-01 21:40:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 4, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Aug 4, 2020): Issue is stale and will be closed in 7 days unless there is new activity

kerem referenced this issue

2026-03-01 21:50:53 +03:00

[PR #152] [MERGED] Include install instructions for nix #1370

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#152

No description provided.

Rows
Columns