-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unfriendly error message Error: EACCES: permission denied, open '/__w/_temp/_runner_file_commands/save_state_e59de318-2ebd-4430-adee-f74fc8e00eb1' #1575
Comments
And it seems like this message is incorrect, even? Unless EACCES is an extremely poor error message for "file does not exist". When I
|
I am becoming more convinced that this may be a bug with the checkout action. Is it fundamentally incompatible with containers where the current user/group ids do not match those of standard github runners? |
Possibly a duplicate of #956 ? |
I started seeing this issue in my project's actions: https://github.com/OpenCyphal/nunavut/actions/runs/9306090562/job/25614627575?pr=333 I was originally using checkout@v3 and just tried upgrading to v4 but the result is the same. |
I started to get it in some of my runs on self-hoster GitHub Actions runners... When using checkout@v3 I got:
...and with checkout@v4:
|
I found this while doing some research and I'm curious if this solves your problem with checkout:
Cheers! |
Not working in my case |
I'm seeing this on one of my self hosted runners too. Was there any resolution or fix to this? |
+1 |
If you are pulling any container image you may need to use root user Basically,
Becomes
This worked for me.. |
I haven't seen this issue in a while now. |
Just got this issue running the checkout action. here's our workflow file:
fails on the checkout action |
When running this action with
container: coqorg/coq:dev
, I seeThis is a pretty unfriendly error message, and I have no idea what command I have to run to fix this issue. I presume I have to do
sudo chmod -R a=u
on some directory, but which one?The text was updated successfully, but these errors were encountered: