Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The runner.temp directory may not exist in a container #20

Open
nilsvu opened this issue Aug 30, 2022 · 2 comments
Open

The runner.temp directory may not exist in a container #20

nilsvu opened this issue Aug 30, 2022 · 2 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@nilsvu
Copy link

nilsvu commented Aug 30, 2022

Running this action in a container fails because the runner.temp directory doesn't exist. Perhaps the temp dir could be passed to the action as an option?

This seems to be related to actions/runner#965.

It looks like only the runner.temp in the tar command incorrectly refers to the host temp directory. The runner.temp in the upload-artifact step correctly points into the container.

@ncfavier
Copy link
Contributor

It looks like only the runner.temp in the tar command incorrectly refers to the host temp directory. The runner.temp in the upload-artifact step correctly points into the container.

Can you link to a workflow run illustrating this?

@nilsvu
Copy link
Author

nilsvu commented Aug 30, 2022

Sure, here's an example: https:/nilsvu/gwpv/runs/8093009319?check_suite_focus=true

Bildschirmfoto 2022-08-30 um 16 50 12

Then after just creating the runner.temp directory manually within the container the tar goes through but the upload fails: https:/nilsvu/gwpv/runs/8093544512?check_suite_focus=true

Bildschirmfoto 2022-08-30 um 16 51 46

So there seems to be some inconsistent handling of runner.temp with containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants