Replies: 5 comments 3 replies
-
I am experiencing this issue as well with the latest version of ARC when I run a GitHub Action step that uses a container:
|
Beta Was this translation helpful? Give feedback.
-
Were you able to resolve this issue? any help is appreciated. |
Beta Was this translation helpful? Give feedback.
-
I'm also getting the same error using 0.8.1. However Nikola seems to hint at it not being an issue: |
Beta Was this translation helpful? Give feedback.
-
I am also getting this error on 0.8.1 and the job fails with some kind of timeout. Error on the GitHUB UI:
It is possible that this is not the main reason. What I can confirm that node with the index.js starts up and runs for a while. It seems that there are no logs coming from index.js so we never learn the actual reason. |
Beta Was this translation helpful? Give feedback.
-
Just noticed the same problem on our on-prem K8s cluster:
|
Beta Was this translation helpful? Give feedback.
-
running a normal job works fine, but when trying to use a service container or specifying a container image in a work flow causes the job to fail with
Failed to update oom_score_adj for PID: 70. [WORKER 2023-08-01 23:48:59Z INFO ProcessInvokerWrapper] System.UnauthorizedAccessException: Access to the path '/proc/70/oom_score_adj' is denied. [WORKER 2023-08-01 23:48:59Z INFO ProcessInvokerWrapper] ---> System.IO.IOException: Permission denied [WORKER 2023-08-01 23:48:59Z INFO ProcessInvokerWrapper] --- End of inner exception stack trace ---
I even copied the exact example from the deep dive video in https://www.youtube.com/watch?v=_F5ocPrv6io
I can connect to the runner and the permissions on /proc look ok, but any attempt to do anything in /proc gives permissions denied even as root or with sudo
the jobs run just fine on hosted runners, and were running just fine using 0.27.4 with runner deployments
.github/workflows/stupid_test.yml
this fails
this does not
values.yaml
Beta Was this translation helpful? Give feedback.
All reactions