conda-anaconda-tos
).
conda-anaconda-tos
augments the existing conda workflow by automatically prompting you to accept the TOS for a given channel when necessary. conda-anaconda-tos
is triggered any time you run a conda command that interacts with channels (e.g., using conda create
, conda search
, conda install
, etc.), but is meant to be unobtrusive to your work.
For more information on conda-anaconda-tos
, see the plugin’s GitHub repository.
conda-anaconda-tos
in your (base)
environment. If you’re unsure if you have conda-anaconda-tos
in your (base)
environment, you can check by running the following command:
conda-anaconda-tos
into your (base)
environment by running the following command:
pandas
. Your command might look like:
https://repo.anaconda.com/pkgs/main
https://repo.anaconda.com/pkgs/r
https://repo.anaconda.com/pkgs/msys2
conda-anaconda-tos
gathers all of the channels in your .condarc
file and reviews them to see if they require you to accept a TOS to use them. For each channel that requires a TOS, you will see:
a
to accept the TOS.r
to reject the TOS.v
to display a link to a website that contains the TOS you’re being asked to accept.conda-anaconda-tos
automatically prompts you when a channel’s TOS needs an acceptance, the plugin also has its own set of commands for viewing and managing TOS for the channels listed in your .condarc
and/or any other channels that you specify:
defaults
and the channels in your channels:
list.rejected
. If accepted, the column will display a timestamp for when the acceptance occurred (see Accepted column).conda-anaconda-tos
plugin displays, accepts, and rejects the TOSes of all channels specified in the defaults
and channels:
lists in your .condarc
file.
Display website URL links to view the text of all applicable TOS:
CI=true
), the plugin will automatically accept Terms of Service and print a warning message. This ensures automated builds don’t get blocked waiting for user input.
CI
environment variable might not be automatically passed to the container, which can lead to unexpected ToS prompts during your CI/CD workflows.
We recommend passing the CONDA_PLUGINS_AUTO_ACCEPT_TOS
environment variable to Docker or explicitly accepting the ToS by running conda tos accept
:
CONDA_PLUGINS_AUTO_ACCEPT_TOS
environment variable to Docker using the Docker CLI:
CI
environment variable will not be automatically passed.
CONDA_PLUGINS_AUTO_ACCEPT_TOS
environment variable to Docker:
CI
variable. However, manually invoked Docker commands within steps do not automatically inherit these variables.conda-anaconda-tos
plugin currently detects CI/CD environments by looking for CI=true
, in order to automatically accept TOS and not cause the workflow to hang while waiting for user input.
CI systems that do not leverage the CI=true
flag are currently experiencing errors because the plugin is waiting for user input to accept TOS. This issue is actively being worked on.
.condarc
file:
conda-anaconda-tos
where you might be prompted to re-accept a TOS you have already accepted after updating conda. This happens because the plugin currently treats package updates the same as uninstalls for security reasons. If you update your conda environment with conda update -n base --all
, the plugin clears your TOS acceptance record as a precaution and you will be prompted again to accept the TOS, when applicable.
conda-anaconda-tos
, which will also clear your TOS acceptance records.Open Anaconda Prompt (Terminal on macOS/Linux) and run one of the following commands: