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
Feature
Ensure that any files / folders that get touched by this action in the mounted workspace have thier permissions fixed back to their original owner (probably the owner of the $GITHUB_WORKSPACE)
Problem
As it stands when you use this action the .terraform folder will have its owner set to root root as the container makes changes to the files (as well as any other file or folder the container creates / updates). This then results in the next run of the workflow failing as the checkout action fails to delete the .terraform folder due to it being owned by root root rather than the user running the actions service.
To wokraround this you can use the action peter-murray/reset-workspace-ownership-action to reset the permissions on the repository code.
- name: Get Actions user idid: get_uidrun: | actions_user_id=`id -u $USER` echo $actions_user_id echo ::set-output name=uid::$actions_user_id
- name: Correct Ownership in GITHUB_WORKSPACE directoryuses: peter-murray/reset-workspace-ownership-action@v1with:
user_id: ${{ steps.get_uid.outputs.uid }}
This is faff though and needs to be done in any workflow that uses this action, it should be handled natively or there be an input that can solve this.
Feature
Ensure that any files / folders that get touched by this action in the mounted workspace have thier permissions fixed back to their original owner (probably the owner of the
$GITHUB_WORKSPACE
)Problem
As it stands when you use this action the
.terraform
folder will have its owner set toroot root
as the container makes changes to the files (as well as any other file or folder the container creates / updates). This then results in the next run of the workflow failing as the checkout action fails to delete the.terraform
folder due to it being owned byroot root
rather than the user running the actions service.To wokraround this you can use the action
peter-murray/reset-workspace-ownership-action
to reset the permissions on the repository code.This is faff though and needs to be done in any workflow that uses this action, it should be handled natively or there be an input that can solve this.
https://vsupalov.com/docker-shared-permissions/ Basically support this problem.
EDIT For posterity's sake this is the type of error you'll get due to docker messing with the permission bits of files / folders it touches:
The text was updated successfully, but these errors were encountered: