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
All dotnet commands fail due to environment variables #510
Comments
Hello @william-dafriend |
@william-dafriend If you are running your action-runner as a service on Linux, make sure the service is installed to use a user account, otherwise it will default to root; where these aren't defined. If you want to use root, then export DONET_CLI_HOME=/tmp and that will get you past this issue. |
Hello @william-dafriend, Thank you for creating the issue and we have investigated the issue. Understood that steps:
We have tested the same in our local, able to set the the environment variables through the workflow and the commands are successful. Please find the screenshot for reference. Please confirm whether you have set the env variables by following the above step in your workflow. |
Hello @william-dafriend, Please confirm whether you have set the env variables by following the above step in your workflow. |
1 similar comment
Hello @william-dafriend, Please confirm whether you have set the env variables by following the above step in your workflow. |
Closing this issue as we don't hear any response from long time. Please feel free to reach us if you are still facing the issue. |
Description:
All attempts at using the action fail with the following error
Task version:
version 4
Platform:
Runner type:
Repro steps:
Attempt to run an action using setup-dotnet/v4 and call any dotnet command
Expected behavior:
commands should complete successfully
Actual behavior:
Comamnds return errors about missing environment variables
All dotnet commands work fine in the _work directory directly on the runner. I have tried explicitly setting HOME and DOTNET_CLI_HOME environment variables in the action itself. These variables are both set and exported for the user on the github runner.
The text was updated successfully, but these errors were encountered: