I’m trying to use the new Container Agent setup on a microk8s (first I appreciate this might be my issue as it likely hasn’t been tested) cluster (k8s v1.22). I can deploy everything successfully with Helm and the container-agent connects to CircleCI successfully and polls for jobs. However, when attempting to run any jobs I get the following error present in the CircleCI UI in a step called ‘Instance Failure’:
could not run task: launch circleci-agent on "container-0" failed: command terminated with exit code 139
So it seems there’s a segmentation fault occurring.
The same error log is reflected in the container-agent pod logs
service-work error=1 error occurred:mode=agent result=error service.name=container-agent service_name=container-agent.
- If I try and set any resource requests or limits for the task containers (like in the example in the docs) then no task containers ever get launched, the jobs just sit there unprocessed and times out after 10 minutes (no task-agent containers ever get created).
- Container agent version is: 1.0.7556-dfb352b
- I can see warnings in the container-agent pod logs:
httpclient: container-agent /api/v2/runner/claim app.loop_name=claim ................ warning=no contentbut I’m unsure what this means.
- If task-agent pods do get spawned they get into a running state in k8s but just sit there doing nothing with no log output whatsoever.
- I also get the
WARN: Missing API Keymessage on the first line of the logs even though the agent seems to be communicating with CircleCI successfully.