`conda env create`#

Create an environment based on an environment definition file.

If using an environment.yml file (the default), you can name the environment in the first line of the file with 'name: envname' or you can specify the environment name in the CLI command using the -n/--name argument. The name specified in the CLI will override the name specified in the environment.yml file.

Unless you are in the directory containing the environment definition file, use -f to specify the file path of the environment definition file you want to use.

usage: conda env create [-h] [-f FILE] [-n ENVIRONMENT | -p PATH] [-C] [-k]
                        [--offline] [--force] [--no-default-packages] [--json]
                        [-v] [-q] [-d] [-y] [--solver {classic}]
                        [remote_definition]

Positional Arguments#

remote_definition: Remote environment definition / IPython notebook

Named Arguments#

-f, --file

Environment definition file (default: environment.yml)

--force

--force is deprecated and will be removed in 24.3. Use --yes instead.

--no-default-packages

Ignore create_default_packages in the .condarc file.

--solver

Possible choices: classic

Choose which solver backend to use.

Target Environment Specification#

-n, --name: Name of environment.
-p, --prefix: Full path to environment location (i.e. prefix).

Networking Options#

-C, --use-index-cache: Use cache of channel index files, even if it has expired. This is useful if you don't want conda to check whether a new version of the repodata file exists, which will save bandwidth.
-k, --insecure: Allow conda to perform "insecure" SSL connections and transfers. Equivalent to setting 'ssl_verify' to 'false'.
--offline: Offline mode. Don't connect to the Internet.

Output, Prompt, and Flow Control Options#

--json: Report all output as json. Suitable for using conda programmatically.
-v, --verbose: Can be used multiple times. Once for detailed output, twice for INFO logging, thrice for DEBUG logging, four times for TRACE logging.
-q, --quiet: Do not display progress bar.
-d, --dry-run: Only display what would have been done.
-y, --yes: Sets any confirmation values to 'yes' automatically. Users will not be asked to confirm any adding, deleting, backups, etc.

Examples:

conda env create
conda env create -n envname
conda env create folder/envname
conda env create -f /path/to/environment.yml
conda env create -f /path/to/requirements.txt -n envname
conda env create -f /path/to/requirements.txt -p /home/user/envname

conda env create#