actions / actions/runner-container-hooks
Log of containers no longer show up
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
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.13.0
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
Take an action that uses services e.g., the one pasted her and run it on arc runners:
pubsub:
name: PubSub only
runs-on: ubuntu-latest
services:
pubsub:
image: thekevjames/gcloud-pubsub-emulator:e852273e07
ports:
- 8681:8681
options: >-
-e PUBSUB_PROJECT1=feldera-test,test_pubsub_input-0
--health-cmd "nc -z 127.0.0.1 8681"
--health-interval 10s
--health-timeout 5s
--health-retries 5
steps:
- name: Checkout repository
uses: actions/checkout@v4
Describe the bug
There are no logs showing up for it in Stop containers:
However, if the action runs under a github action runner e..g, ubuntu-latest, I see the following output:
I'm using containerMode kuberenets in helm
containerMode:
type: "kubernetes"
Describe the expected behavior
I am pretty sure logs showed up in past version (i'd expect the behavior to be similar to ubuntu-latest)
Additional Context
n/a
Controller Logs
n/a
Runner Pod Logs
n/a
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 workflow's services definition and the Helm containerMode: kubernetes configuration, then reproduce on controller version 0.13.0 while comparing it with ubuntu-latest. Investigate how service-container output is handled for Stop containers; done means the service logs appear there as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, helm, kubernetes, typescript
- Domain
- ci-cd, devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100