-
Notifications
You must be signed in to change notification settings - Fork 129
Problems with self-hosted runners #91
Comments
Fixed Lines 52 to 54 in 992f4d7
|
Can you elaborate and provide reproduction steps?
|
When a container runs, it uses the root user by default, that new files created in a container will be added to a runner with root user permissions. jobs:
pull-request:
runs-on: [ self-hosted, Linux ]
steps:
- uses: actions/checkout@v3
- uses: docker://ghcr.io/repo-sync/pull-request:v2.8
with:
destination_branch: "main"
github_token: ${{ secrets.GITHUB_TOKEN }} |
Same problem here, the workflow cannot run twice. Second run fails to delete files created with the root user by the first run. |
The permission issue with self-hosted runners is a general issue that happens to all docker based actions on self-hosted runners. You can find discussions, solutions, and provide feedback at actions/runner#434 I'm going to mark this as a wontfix for now but open to revisit in the future. |
Added a section to README: Docker Container Image Usage |
There are two problems with self-hosted runners:
The first problem is solved by building a docker image and referencing it in a workflow:
The second problem is solved by passing USER_ID parameter in a container:
Here is my pull request as an example #90
The text was updated successfully, but these errors were encountered: