Summary of errors reported when using YML file to migrate CONDA environment

Write at the top , This is a failure summary , In the end because Found conflicts! Looking for incompatible packages. Take too long , I gave up , Choose to install the package directly on the new server .

Use yml Document carried out conda Environmental migration
use first export Option to generate a environment.yml file , Between different platforms and operating systems Reproduce the project environment .environment.yml Files are not specific to a particular operating system , And use YAML Format .environment.yml Only the package name is listed , from conda Build the environment based on the name of the package . export It also includes the use of pip Installed packages .

step1: export environment.yml file ：

 conda env export > environment.yml

Be careful ： If the current path already has environment.yml file ,conda Will rewrite this file
step 2: Recreate the environment

 conda env create -f environment.yml

Report a mistake ： AttributeError: ‘NoneType’ object has no attribute ‘keys’ conda env

Check your envinroment.yml file , This is basically because yml Empty or broken. Regenerate it yml try .

Error reporting II ：CondaValueError: prefix already exists: /home/username/anaconda3

This is because yml Medium env name It's empty , Or with the present machine env Conflict .
For example, the following yml Medium env name by base, And each conda It's all down there base This environment , There is a conflict .
terms of settlement ：
modify yml Medium name, Or add... To the command -n Parameters indicate env name

 conda env create -f environment.yml -n envname

Error reporting 3 、Found conflicts! Looking for incompatible packages. failed

Found conflicts! Looking for incompatible packages. failed
conda It takes a long time Looking for incompatible packages It shows failed, Then again Looking for incompatible packages...
terms of settlement ：conda update anaconda

Error reporting 4 、ResolvePackageNotFound

The solution is to delete the second equal sign and the following and configuration information in the error package
Reference resources https://blog.csdn.net/Hunter_Murphy/article/details/124783101

It takes a long time Looking for incompatible packages, Lose patience , The final decision is to pack directly .