Override the init-dind-externals init container in the runner set helm chart
ecooke-macu opened this issue · comments
Checks
- I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
- I am using charts that are officially provided
Controller Version
0.9.1
Deployment Method
Helm
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions).
- I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
To Reproduce
Create a values.yaml
Specify init container for init-dind-externalsDescribe the bug
The default init-dind-externals container doesn't get overwritten and is stuck on the default.
Describe the expected behavior
Able to override the init-dind-externals container
Additional Context
We need to stop the logging of all files copied. Currently it logs about 20k lines each time the container starts. We need to remove the `-v` from the `cp`.Controller Logs
Org policies don't allow internal logs to be publicly available. I can provide them privately though.Runner Pod Logs
Org policies don't allow internal logs to be publicly available. I can provide them privately though.
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
Hey @edwardcookemacu,
Please refer to my comment here. This behavior is well documented and explained in various links I linked. Closing this issue now.
Thank you! That pointed me in the right direction.