Open bquenin opened 2 years ago
I believe there might be a sanitization bug in the portmapping of containerMode: kubernetes
.
Instead of 6379/tcp
, does 6379
(tcp is default) or 6379:6379/tcp
work?
I met the same issue too. I built a new action runner image with new RUNNER_CONTAINER_HOOKS_VERSION=0.2.0
.
All the following cases failed.
6379
6379:6379
6379:6379/tcp
Any updates here?:) Facing the same problem.....
While the exact error is different than what is descibed here, @Brenner87 and I have been unable to use GHA sidecar containers in containerMode: kubernetes
as well, read more here: https://github.com/actions/actions-runner-controller/discussions/2227
But it seems to be completely nuking the entrypoint command to start the sidecar container for us, having nothing to do with ports.
I got this error too, and it turns out to be related to our OPA policy to require resources on all containers,
it tooks days for me to figure our the root cause but it's really a tiny issue, the real problem is with the error message, I updated this line to provide detailed error info:
# from
throw new Error(`failed to create job pod: ${err}`)
# to
throw new Error(`failed to create job pod: ${JSON.stringify(err)}`)
then, instead of "HTTP Error", you'll get log like this;
Error: Error: failed to create job pod: {"response":{"statusCode":403,"body":{"... is forbidden: failed quota: fuze-quota: must specify cpu for: job; memory for: job","reason":"Forbidden","..."statusCode":403,"name":"HttpError"}
You may get a different error, but I'm sure you'll know how to fix it :)
I have packaged a fixed version of Docker image here https://hub.docker.com/r/kacifer/actions-runner, specify image in the controller deployment or your runner spec: kacifer/actions-runner:0.0.2
(I'm not keeping this image up to date, you could package your own easily).
@kacifer have you considered a PR against https://github.com/actions/runner-container-hooks? Seems like it'd be worth it. I just ran into this error when I tried to have the worker
pod use a service account that didn't exist. Would have been handy to get the full error message here.
@stephen-tatari yes I could do that, glad to know someone else have the same problem š¤”
Any update on the core issue here? Is it possible to run a job that creates services
with a containerMode: kubernetes
?
@kacifer could you elaborate on the solution you have found? I can't find any PR open to fix this
Following the error messages OP received, it seems to me like it's a configuration issue. This thread #3073 lead me to test service containers with localhost, which works fine!
Just posting this here in case anybody comes here because of the issue title. It does not appear to be a general problem.
Controller Version
0.25.2
Helm Chart Version
0.20.2
CertManager Version
1.9.1
Deployment Method
Helm
cert-manager installation
Yes I've followed https://github.com/actions-runner-controller/actions-runner-controller#installation and installed cert-manager from the official source https://cert-manager.io/docs/installation/helm/
Checks
Resource Definitions
To Reproduce
Describe the bug
The initialize container step fails:
Describe the expected behavior
Hi,
I'm trying to use a
service
container in a job. I was expecting the service container to be created as an additional container to the pod executing this job but it looks like it's not working. Is there anything I'm missing?Controller Logs
Runner Pod Logs