You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Previously (2.295.0), docker createwas 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.
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.
The text was updated successfully, but these errors were encountered:
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:
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 withRunner_
and the worker logs are prefixed withWorker_
. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.The text was updated successfully, but these errors were encountered: