actions / actions/runner-container-hooks
Environment Variables with ARC
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
If ACTION_RUNNER_USE_KUBE_SCHEDULER=true and the runner-pod and workflow-pod to be scheduled on different nodes the following occurs:
- GitHub environment variables (e.g., echo "var=something" >> $GITHUB_ENV) do not get passed or populated in the subsequent steps.
I think this is a container hook problem, if this isn't the correct repo let me know and I'll try to create the issue in the proper repo.
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
Reproduce the failure with ACTION_RUNNER_USE_KUBE_SCHEDULER=true while the runner-pod and workflow-pod use different nodes. Start by tracing the container hook behavior around GITHUB_ENV propagation; done means variables written in one step are available in subsequent steps under this scheduling setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100