You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the asyncapi/cli GitHub Action on a non-root self-hosted runner, the permissions of the files in the mounted directories are messed up.
This seems to be a common issue when running docker containers as root on self-hosted runners, see actions/runner#434.
Expected behavior
The docker container is using the same UID as the runner and the permissions of the mounted directories remain unchanged.
Screenshots
How to Reproduce
Setup a non-root self-hosted runner
Use the asyncapi/cli action in a workflow with a checkout beforehand
Run the workflow, it should succeed
Run the workflow, it should fail on the checkout step
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Describe the bug.
When running the asyncapi/cli GitHub Action on a non-root self-hosted runner, the permissions of the files in the mounted directories are messed up.
This seems to be a common issue when running docker containers as root on self-hosted runners, see actions/runner#434.
Expected behavior
The docker container is using the same UID as the runner and the permissions of the mounted directories remain unchanged.
Screenshots
How to Reproduce
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
None
The text was updated successfully, but these errors were encountered: