Skip to content

troubleshooting.rst

Latest commit

 

History

History
221 lines (136 loc) · 8.2 KB

troubleshooting.rst

File metadata and controls

221 lines (136 loc) · 8.2 KB

Troubleshooting

Please use the official installer

Please make sure that you use the :ref:`official Mambaforge installer <mamba-install>` to install Mamba. Other installation methods are not supported.

Mamba should be installed to the base environment

Installing Mamba to an environment other than base is not supported. Mamba must be installed in the base environment alongside Conda, and no other packages may be installed into base.

No other packages should be installed to base

Installing packages other than Conda and Mamba into the base environment is not supported. Mamba must live in the same environment as Conda, and Conda does not support having packages other than Conda itself and its dependencies in base.

Using the defaults channels

It is not recommended to use the Anaconda default channels:

  • pkgs/main
  • pkgs/r / R
  • msys2
  • defaults (which includes all of the above)

Please note that we won't be able to help resolving any problems you might face with the Anaconda channels.

To check if you have any Anaconda default channels in your configuration, use:

$ mamba info
...
channel URLs : https://repo.anaconda.com/pkgs/... # BAD!
               ...
               https://conda.anaconda.org/conda-forge/...
...

Please change your configuration to use only conda-forge using one of the following methods.

Disable the default channels in your install commands:

mamba install --override-channels ...

Or your :file:`environment.yml` file:

name: ...
channels:
  - ...
  - nodefaults

Or in your :file:`~/.condarc` file:

...
channels:
  - ...
  - defaults  # BAD! Remove this if it exists.
  - nodefaults

Mixing the defaults and conda-forge channels

The Anaconda default channels are incompatible with conda-forge.

Using the default and conda-forge channels at the same time is not supported and will lead to broken environments:

# NOT supported!
channels:
  - conda-forge
  - defaults

Mamba broken after Conda update

Mamba sometimes stops working if you update to a very recent version of Conda. Please downgrade to the latest working a version and file a bug report in the Mamba bug tracker if the problem has not been reported yet.

Mamba or Micromamba broken after an update

While we make our best effort to keep backward compatibility, it is not impossible that an update breaks the current installation. The following actions can be tried:

  • Reinitializing your shell with micromamba shell reinit.
  • Deleting the package cache ("package cache" entries in micromamba info)

libmamba.so.2: undefined symbol ...

See :ref:`defaults_channels`.

Windows long paths

Windows API historically supports paths up to 260 characters. While it's now possible to used longer ones, there are still limitations related to that.

libmamba internally relies on \\?\ prefixing to handle such paths. If you get error messages advertising such prefix, please have look at the following steps:

Long paths support has to be activated

source: Robocop troubleshooting documentation

  1. Open the Local Group Policy Editor application: - Start --> type gpedit.msc --> Enter:
  2. Navigate to Computer Configuration > Administrative Templates > System > Filesystem. On the right, find the "Enable win32 long paths" item and double-click it
  3. Change the setting to Enabled
  4. Exit the Local Group Policy Editor and restart your computer (or sign out and back in) to allow the changes to finish

If the problem persists after those steps, try the following:

  1. Open the Registry Editor application: - Start --> type regedit.msc and press Enter:
  2. Navigate to HKEY-LOCAL-MACHINE > SYSTEM > CurrentControlSet > Control > FileSystem. On the right, find the LongPathsEnabled item and double-click it
  3. Change the Value data: to 1
  4. Exit the Registry Editor

cmd.exe does not support calls to long prefixes

While cmd.exe shell support long paths prefixing for directory operations such as dir, it doesn't allow to call an executable or a batch file located at a long path prefix.

Thus, the following cases will fail:

  • completely
    • calling executables located at long prefixes
    • installation of packages with pre/post linking or activation .bat scripts
  • partially
    • pre-compilation of noarch packages, with no impact on capability to use the package but removing it will let artifacts (pycache) on the filesystem

Hangs during install in QEMU

When using Mamba/Micromamba inside a QEMU guest, installing packages may sometimes hang forever due to an issue with QEMU and glibc. As a workaround, set G_SLICE=always-malloc in the QEMU guest, eg.:

export G_SLICE=always-malloc
mamba install ...

See #1611 for discussion.

Hangs during package installation on NFS (Network File Systems)

When using Mamba/Micromamba in a environment with NFS, package installation (e.g., NumPy) may hang at the step when libmamba attempts to lock a directory. A solution is to update the Mamba/Micromamba configuration to not use lockfile by the command:

micromamba config set use_lockfiles False

See #2592, #1446, #1448, #1515 for more details.

"libmamba Download error (7) Could not connect to server"

mamba install and other mamba commands yield said errors. This might be due to being flagged by an antivirus. A solution is to whitelist the appropriate folders and files; see #3979 for more details.

SSL Certificate Verification Issues

SSL/TLS certificate verification errors

If you encounter SSL certificate verification errors, especially in corporate environments with MITM HTTPS proxies, you have several options:

Use the OS trust store (Recommended for corporate environments)

Set ssl_verify to truststore to use your operating system's certificate trust store. This is particularly useful when your organization has installed custom CA certificates in the system trust store:

micromamba config set ssl_verify truststore

Or in your :file:`~/.condarc` or :file:`~/.mambarc` file:

ssl_verify: truststore

On Windows, this uses the Windows certificate store via Schannel. On macOS and Linux, this uses the system certificate paths.

Use a custom certificate file

If you have a specific CA certificate bundle, you can point to it directly:

micromamba config set ssl_verify /path/to/cacert.pem

Or set the REQUESTS_CA_BUNDLE environment variable:

export REQUESTS_CA_BUNDLE=/path/to/cacert.pem

Disable SSL verification (Not recommended)

Warning

Disabling SSL verification is not recommended as it exposes you to security risks including man-in-the-middle attacks.

Only use this for testing or if you understand the security implications:

micromamba config set ssl_verify false

See #2857 for more details on corporate proxy environments.