- The conda configuration file (.condarc)
- General configuration
- Channel locations (channels)
- Update conda automatically (auto_update_conda)
- Always yes (always_yes)
- Show Channel URLs (show_channel_urls)
- Change command prompt (changeps1)
- Add PIP as Python Dependency (add_pip_as_python_dependency)
- Use PIP (use_pip)
- Configure conda for use behind a proxy server (proxy_servers)
- Offline mode only (offline)
- Advanced configuration
- Conda build configuration
- Specify conda build output root directory
- Automatically upload conda build packages to Anaconda.org (anaconda_upload)
- Token to be used for Anaconda.org uploads (conda-build 3.0+)
- Limit build ouptut verbosity (conda-build 3.0+)
- Disable filename hashing (conda-build 3.0+)
- Disable recipe and package verification (conda-build 3.0+)
- Disable per-build folder creation (conda-build 3.0+)
- Skip building packages that already exist (conda-build 3.0+)
- Omit recipe from package (conda-build 3.0+)
- Disable activation of environments during build/test (conda-build 3.0+)
- PyPI upload settings (conda-build 3.0+)
- PyPI repository to upload to (conda-build 3.0+)
The conda configuration file (.condarc) is an OPTIONAL runtime configuration file which allows advanced users to configure various aspects of conda, such as which channels it searches for packages, proxy settings, environment directories, and so on.
A .condarc file is not included by default, but it is automatically created in
the user’s home directory the first time you run the
conda config command.
A .condarc file may also be located in the root environment, in which case it overrides any in the home directory.
Note: A .condarc file can also be used in an administrator-controlled installation to override the users’ configuration. Please see Centralized installation.
The conda configuration file can be used to change:
- Where conda looks for packages
- If and how conda uses a proxy server
- Where conda lists known environments
- Whether to update the bash prompt with the current activated environment name
- Whether user-built packages should be uploaded to Anaconda.org
- Default packages or features to include in new environments
- And more.
To create or modify a .condarc configuration file, from the command line, use
conda config command, or use a text editor to create a new file named
.condarc and save to your user home directory or root directory.
conda config --add channels conda-forge
SEE ALSO: For a complete list of conda config commands available, see the
command reference. The same list is available
at the command prompt by typing
conda config --help.
The .condarc configuration file follows simple YAML syntax.
Download a sample .condarc file to edit in your editor and save to your user home directory or root directory.
TIP: Conda supports tab completion with external packages instead of internal configuration.
For more configuration information see: http://continuum.io/blog/advanced-conda-part-1#configuration
Listing channel locations in the .condarc file will override conda defaults, causing conda to search only the channels listed here, in the order given.
defaults to automatically include all default channels. Non-url channels
will be interpreted as Anaconda.org usernames, and this can be changed by modifying
channel_alias key as explained below. The default is just
channels: - <anaconda_dot_org_username> - http://some.custom/channel - file:///some/local/directory - defaults
To select channels for a single environment, put a
.condarc file in the root
directory of that environment. If you have installed Miniconda with Python 3 in
your home directory and the environment is named “flowers”, the path may be
~/miniconda3/envs/flowers/.condarc, and for other conda installations the
path will be similar.
When True, conda updates itself any time a user updates or installs a package
in the root environment. When False, conda updates itself only if the user
manually issues a conda update command. The default is
True. You can edit
the .condarc file or set the option with a command such
conda config --set auto_update_conda False.
Choose the yes option whenever asked to proceed, such as when installing. Same
as using the
--yes flag at the command line. The default is
Show channel URLs when displaying what is going to be downloaded and
conda list. The default is
activate, change the command prompt (
$PS1) to include the activated
environment. The default is
Add pip, wheel and setuptools as dependencies of python. This ensures pip, wheel
and setuptools will always be installed any time python is installed.
The default is
Use pip when listing packages with
conda list. Note that this does not affect
any conda command or functionality other than the output of the
conda list. The default is
By default, proxy settings are pulled from the
environment variables or the system. Setting them here overrides that default.
To give a proxy for a specific scheme and host, use the scheme://hostname form for the key. This will match for any request to the given scheme and exact hostname.
proxy_servers: 'http://10.20.1.128': 'http://10.10.1.10:5323'
Note: If you do not include the username and password, of if authentication fails, conda will prompt for a username and password.
Note: If your password contains special characters they will need to be escaped as follows: https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters
Note: Be careful not to use
http when you mean
https when you mean
Note: If you are behind a proxy that does SSL inspection such as a Cisco IronPort Web Security Appliance (WSA),
it may be necessary to override the SSL verification settings using
ssl_verify as described in SSL verification (ssl_verify).
conda install --channel asmeurer <package> is the same
conda install --channel https://conda.anaconda.org/asmeurer <package>. This
is because the default
channel_alias is https://conda.anaconda.org/ . Whenever
conda is given a channel name that is not a URL, it prepends the
to the front of the name it was given.
You can set the
channel_alias to your own repository. If your repository is at
conda install --channel jsmith <package> would be
the same as
conda install --channel https://yourrepo.com/jsmith <package> .
NOTE: For Windows users, the slash (/) at the end of a URL is required. Example https://your.repo/conda/
When creating new environments add these packages by default. You can override
this option at the command prompt with the
--no-default-packages flag. The
default is not to include any packages.
create_default_packages: - ipython
Enable certain features to be tracked by default. The default is to not track
any features. This is similar to adding
mkl to the
track_features: - mkl
conda install updates the given package and all its
dependencies to the latest versions.
If you prefer to only update the packages given explicitly at the command line
and avoid updating existing installed packages as much as possible, you can
Note that conda will still ensure that dependency specifications are
satisfied, so some dependencies may still be updated, or, conversely, this may
prevent packages given at the command line from being updated to their latest
versions. You can always specify versions at the command line to force conda
to install a given version (like
This option can also be enabled or disabled at the command line with the
To avoid updating only specific packages in an environment, a better option may be to pin them. See Pinning packages for more information.
Build output root directory. This can also be set with the
environment variable. The default is
<CONDA_PREFIX>/conda-bld/, or if you do
not have write permissions to
conda-build: root-dir: ~/conda-builds
Automatically upload packages built with
conda build to Anaconda.org. The
Tokens are a means of authenticating with anaconda.org without needing to login. You can pass your token to conda-build with this condarc setting, or with a CLI argument. This is unset by default. Setting it implicitly enables anaconda_upload.
conda-build: anaconda_token: gobbledygook
Conda-build’s output verbosity can be reduced with the
quiet setting. For
more verbosity use the CLI flag
conda-build: quiet: true
Conda-build 3 adds hashes to filenames to allow greater customization of dependency versions. If you find this disruptive, you can disable the hashing with the following config entry:
conda-build: filename_hashing: false
Note that conda-build does no checking when clobbering packages, and if you utilize conda-build 3’s build matrices with a build configuration that is not reflected somehow in the build string, you will be missing packages due to clobbering.
By default, conda-build uses conda-verify to ensure that your recipe and package meet some minimum sanity checks. You can disable these:
conda-build: no_verify: true
By default, conda-build creates a new folder for each build, named for the
package name plus a timestamp. This allows you to do multiple builds at once. If
you have issues with long paths, you may need to disable this behavior. You
should first try to change the build output root directory with the
setting described above, but fall back to this as necessary:
conda-build: set_build_id: false
By default, conda-build builds all recipes that you specify. You can instead skip recipes that are already built. A recipe is skipped if and only if all of its outputs are available on your currently configured channels.
conda-build: skip_existing: true
By default, conda-build includes the recipe that was used to build the package. If this contains sensitive or proprietary information, you can omit the recipe.
conda-build: include_recipe: false
Note that if you do not include the recipe, you cannot use conda-build to test
the package after the build completes. This means that you cannot split your
build and test steps across two distinct CLI commands (
conda build --notest
conda build -t recipe). If you need to omit the recipe and
split your steps, your only option is to remove the recipe files from the
tarball artifacts after your test step. Conda-build does not provide tools for
By default, conda-build activates the build and test environments prior to executing the build or test scripts. This adds necessary PATH entries, and also runs any activate.d scripts you may have. If you disable activation, the PATH will still be modified, but the activate.d scripts will not run. This is not recommended, but some people prefer this.
conda-build: activate: false
Unset by default. If you have wheel outputs in your recipe, conda-build will try to upload them to the PyPI repository specified by the
pypi_repository setting using credentials from this file path.
conda-build: pypirc: ~/.pypirc