-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
conda command not found #3477
Comments
Hello @Bengt. Thank you for your report. We will take a look. |
Hello @dibir-magomedsaygitov. Thanks for looking into this. I am now done filling in the bug report form. |
Hello @Bengt. Thank you for your report. We have preinstalled |
Hello @dmitry-shibanov. Thanks for looking into this. I will try the setup-conda task. What does this mean for this issue, though? Would it be sensible to add the preinstalled miniconda to the PATH as well or is there a reason not to do that? |
We shouldn't add miniconda to PATH because it will cause conflicts with pre-installed Python. Using action - is recommended way. |
Hello @maxim-lobanov. Thanks for the explanation. Since the conda command is intentionally not in PATH, we can consider this issue closed as "won't fix" or so. Since the design decision of not adding conda to the PATH was not obvious to me, others will likely also stumble upon that. I was looking at the environment documentation, which list miniconda as preinstalled.[1, 2] So, I falsely assumed miniconda was also in PATH. Interestingly, there are notes about MSYS2 being installed, but not in PATH.[3, 4] Should the miniconda setup be documented similarly? 1: https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md 3: https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md#msys2 |
@maxim-lobanov @AlenaSviridenko Looks like it's a good idea to update our docs to avoid such confusion in the future |
Agreed to add such note to our README docs. |
This should avoid confusion as documented in actions#3477
This should avoid confusion as documented in actions#3477
Hello @Bengt. Pull request was merged. Changes will be added in the next images rollout. |
Hello @dmitry-shibanov. Awesome! Thanks for extending the documentation. |
Hello @Bengt. Documentation was updated. I'm closing the issue. |
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Conda is installed on the runner by default, but we need to do additional setup <actions/runner-images#3477 (comment)> to make it available on the command line.
Description
I cannot run the conda command in any shell.
Question, Bug, or Feature?:
Bug
Virtual environments affected
Image version
20210516.0
Expected behavior
conda command is available in PATH.
Actual behavior
conda is somehow not available in PATH.
Repro steps
Source: https://github.com/Bengt/multisensor-pipeline/runs/2694187190 (Shell: BASH)
Source: https://github.com/Bengt/multisensor-pipeline/runs/2694001593 (Shell: Powershell)
Source: https://github.com/Bengt/multisensor-pipeline/runs/2695775890 (Shell: cmd)
The text was updated successfully, but these errors were encountered: