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
Hi!
I tried to do something similar to prevent self-hosted runners from filling up the filesystem and came across your action.
If I use the action I am getting a permission denied error on trying to remove the files. Apparently the docker run does not have sufficient access to the _work dir.
Can this be fixed somehow?
Proposal:
Add a cleanup.sh to the image with the rm -rf command and call the cleanup.sh in the action.yml via run.post-entrypoint: '/cleanup.sh'. This ensures that the cleanup task is always run after the workflow is done, wether it fails or not.
The text was updated successfully, but these errors were encountered:
Hi!
I tried to do something similar to prevent self-hosted runners from filling up the filesystem and came across your action.
If I use the action I am getting a
permission denied
error on trying to remove the files. Apparently thedocker run
does not have sufficient access to the_work
dir.Can this be fixed somehow?
Action log from my workflow:
Proposal:
Add a
cleanup.sh
to the image with therm -rf
command and call thecleanup.sh
in theaction.yml
viarun.post-entrypoint: '/cleanup.sh'
. This ensures that the cleanup task is always run after the workflow is done, wether it fails or not.The text was updated successfully, but these errors were encountered: