actions / actions/actions-runner-controller
Getting RUNNER_NAME must be set error for the docker container. The runners are deployed using RunnerDeployment.yaml in Openshift
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Checks
- I've already read https://github.com/actions/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.
- I'm not using a custom entrypoint in my runner image
Controller Version
actions-runner-controller-0.22.0
Helm Chart Version
actions-runner-controller-0.22.0
CertManager Version
No response
Deployment Method
Helm
cert-manager installation
Installation is done without cert-manager
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
- I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
- My actions-runner-controller version (v0.x.y) does support the feature
- I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
- I've migrated to the workflow job webhook event (if you using webhook driven scaling)
Resource Definitions
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: example
spec:
replicas: 1
template:
spec:
enterprise: runner-sample
labels:
- runner
To Reproduce
NA
Describe the bug
Error : RUNNER_NAME must be set in docker container. and runner is failing because it not able to resolve the docker endpoint as the docker container is terminating.
Describe the expected behavior
NA
Whole Controller Logs
NA
Whole Runner Pod Logs
NA
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied RunnerDeployment resource and the actions-runner-controller troubleshooting guide, then inspect the runner and controller logs for the RUNNER_NAME failure. Reproduce the deployment with controller and Helm chart version 0.22.0 on OpenShift; done means the runner container receives RUNNER_NAME, resolves its Docker endpoint, and remains running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100