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

Environment variable "HOME=/github/home" now becomes "HOME" for self-hosted runner #2104

Closed
coiby opened this issue Sep 6, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@coiby
Copy link

coiby commented Sep 6, 2022

Describe the bug
Previously (2.295.0), docker create was executed with -e "HOME=/github/home" now it is executed with -e "HOME". It seems this is reason why the job container failed to start as this is only difference between the jobs run by runner 2.295.0 and 2.296.1 respectively.

To Reproduce
Steps to reproduce the behavior:

  1. re-run this job

Expected behavior

The runner call docker create with -e "HOME=/github/home"

Runner Version and Platform

Version of your runner?
2.296.1

OS of the machine running the runner? OSX/Windows/Linux/...
Linux

What's not working?

Emulated Docker CLI using podman fails with the error "no such file or directory".

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

@coiby coiby added the bug Something isn't working label Sep 6, 2022
@thboop
Copy link
Collaborator

thboop commented Sep 6, 2022

Thanks for the report, we are working on a fix!

@nikola-jokic
Copy link
Contributor

Hey, I will close this issue now since it has been resolved with the runner version 2.296.2. Thank you @coiby for letting us know!

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

No branches or pull requests

3 participants