Replies: 4 comments
-
The docker container logs have some errors:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I also get the same with:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I've hit some job resource limitations with github actions using github runners for an open project. The 6 hours/7GB is too restrictive for some intensive tests :-(
Whilst one approach is to deploy to an external k8s cluster and just manage the deployment/data capture from the runner, I wondered about using a custom runner instead, just to see what it would take
So I've just deployed the action-runner-controller to an Openshift 4.11 cluster. I added the 'privileged' scc, and it's able to create runners as I want. I can customize memory, cpu requirements etc in the CR.
However whilst the runners go Idle, then active, and start executing my actinos, I find that my 'kind' action
just hangs/times out.
I initially tried with a simple CR, then added additional resources, then specific docker config, but still get the issue.
Any ideas?
From the action log, it would appear to be a docker issue:
It appears to be a timeout sometime after:
I realise this is kind-a a kind question, but the same action is working fine on github hosted runners
I haven't yet found more detail on the pods running the runners yet.. still looking
Beta Was this translation helpful? Give feedback.
All reactions