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
I have read the latest README and followed the instructions.
I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.
Describe your proposal
Due to the use of self-hosted actions-runner, which are also suitable for cluster deployment, our containers are run without a specific user. These do not have a home directory and also do not have root-level rights. Therefore, during a deployment, the following ERROR always occurred:
Error: action failed with "EACCES: permission denied, mkdir '/actions_github_pages_1666106344373'"
Describe the solution you'd like
Changing the environment variable env.Home to a folder that has appropriate permissions brought a quickfix here.
However, it would be nicer if the Temp directory will be used instead of the Home directory (linux: /tmp, windows: %appdata%/Local/Temp) or the current working directory of the actions runner was read via PWD.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Describe your proposal
Due to the use of self-hosted actions-runner, which are also suitable for cluster deployment, our containers are run without a specific user. These do not have a home directory and also do not have root-level rights. Therefore, during a deployment, the following ERROR always occurred:
Error: action failed with "EACCES: permission denied, mkdir '/actions_github_pages_1666106344373'"
Describe the solution you'd like
Changing the environment variable env.Home to a folder that has appropriate permissions brought a quickfix here.
However, it would be nicer if the Temp directory will be used instead of the Home directory (linux: /tmp, windows: %appdata%/Local/Temp) or the current working directory of the actions runner was read via PWD.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: