RUNNER_TEMP not mounted in docker based actions
@nikola-jokic is already working on this.
Since Jul 7, 2022.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Env var RUNNER_TEMP points to /home/runner/work/_temp but this directory is not mounted on docker based actions. Contents from previous job steps that are output to this directory is therefore not available. An example is Azure/aks-set-context which stores the resulting kubeconfig in kubeconfig_[timestamp] directly under RUNNER_TEMP. This kubeconfig is therefore not available in docker actions.
Steps to reproduce the behavior:
- Use Azure/aks-set-context
- Use a docker action relying on kubeconfig
Expected behavior
Docker action should have the RUNNER_TEMP directory mounted at the same path.
Runner Version and Platform
Current runner version: '2.294.0'
Operating System
Ubuntu
20.04.4
LTS
What's not working?
"kubectl" config use-context my-context
W0707 12:34:48.857696 29 loader.go:221] Config not found: /home/runner/work/_temp/kubeconfig_1657197285854
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.