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
In the context of using github action runners in kubernetes sith scalesets, on our premisses, we recently saw this error happening at checkout.
It is happening randomly, with most runners working fine
What is the meaning of the error?
Expected behavior
All workflows should properly complete
Observed behavior
No response
Action YAML
I don't think the workflows are relevant, since most times it simply works.But i can provide them if needed
Log output
Error: TypeError: Converting circular structure to JSON
--> starting at object with constructor 'ClientRequest'
| property 'socket' -> object with constructor 'TLSSocket'
--- property '_httpMessage' closes the circle
Error: Process completed with exit code 1.
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.
Additional information
We are using github scaleset runners in kubernetes mode with version 0.10.1
The text was updated successfully, but these errors were encountered:
Thank you for opening an issue. Our team will triage this as soon as we can. Please take a moment to review the troubleshooting steps which lists common error messages and their resolution steps.
Are these self-hosted runners? Line 12 is not part of google-github-actions/auth (/home/runner/k8s/index.js). As per the error message, you need to talk to your administrator:
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
We cannot debug configuration issues with GitHub Actions self-hosted runners (sorry)!
TL;DR
Hi,
In the context of using github action runners in kubernetes sith scalesets, on our premisses, we recently saw this error happening at checkout.
It is happening randomly, with most runners working fine
What is the meaning of the error?
Expected behavior
All workflows should properly complete
Observed behavior
No response
Action YAML
Log output
Additional information
We are using github scaleset runners in kubernetes mode with version 0.10.1
The text was updated successfully, but these errors were encountered: