mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1822] mkdir /.m2 permission denied #888
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#888
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 @andre15silva on GitHub (May 25, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1822
Bug report info
Command used with act
Describe issue
I am trying to run act on the latest commit of https://github.com/perwendel/spark.
Locally, in my machine, I am able to do so without any errors.
However, when I try to run it on a server, it fails due to lack of permission to create a new directory in the root directory of the docker container.
I have tried searching for similar issues, but no solution worked so far.
Thanks in advance :))
Link to GitHub repository
https://github.com/perwendel/spark
Workflow content
Relevant log output
Additional information
No response
@andre15silva commented on GitHub (May 25, 2023):
We (cc @Nfsaavedra) have narrowed down this issue to the Linux user identifiers.
In our local machines, since we are the only and first users of the machine, our users have a uid of 1000.
This is the same uid of user
runneradmininside thecatthehacker/ubuntu:full-latestcontainers.When we execute the same command on remote servers (where our uids are different from 1000), we observe this error.
Even when we set it to run on
-u 1000:1000, it still reports other errors that we suspect are related with permissions too (since we are trying to execute with a uid different from our own).We are patching this issue locally by adding a layer on top of the original image, but this is sub-optimal.
Would you have a proper solution alternative to patch this bug in act?
@github-actions[bot] commented on GitHub (Nov 22, 2023):
Issue is stale and will be closed in 14 days unless there is new activity