-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conda env create fails using environment.yml file. #9480
Comments
Seems like those packages don't exist at that combination of version and build on the channels searched by your target system. I found broadening my search by eliminating build info helped. The command I used was |
Ok, I will try that. Though, I don't understand why the packages should not be available, since I also installed them at the source system. |
The error changed a bit.
|
That was my experience as well: fixed around half the unresolved dependencies. FWIW, my eventual fix was installing the stubborn ones via pip. |
Any updates on this? Going through the same issue. |
same here |
This helped me: datitran/object_detector_app#41 |
Had that issue and solved it by first Guess for me the problem was that the base env conda on remote had packages installed that were not working with the older packages on the host system. |
We hope to solve this like in this issue: ContinuumIO/anaconda-issues#9480
Does anyone here know why we have any Python packages in the top section "dependencies". It seems like it only causes problems. Why not put them all under "pip" |
I think there is a small error in https://github.com/ContinuumIO/anaconda-issues/issues/9480#issuecomment-444117929 namely that
should instead be written as
|
One could also try adding a conda channel if the said packages are not present in the default channels. E.g. qutip package appears in conda-forge channel. One can add the channel by typing the following command. |
I think it also helps to remove any packages which would not be necessary to prevent conflicts. One thing that we must try is by removing the version numbers associated with the packages in the .yml file. |
putting them under dependencies causes anaconda to try and keep the versions compatible after installation, so if you were to install any further packages, then conda would keep them compatible. If you put them all under pip, then they are all installed via pip and would no longer be compatibility controlled by anaconda. You could theoretically do that if you knew that you were never going to need to install another package, but otherwise, I'd say it's probably a bad idea. |
Beware of dependencies in your |
Please see @iggy12345 answer above on why not to do this. |
any updates on this?? |
solved with the EthiopianOne solution: Guys, Simple Answer, |
Please see my above response on why that doesnt solve the issue |
It would be possible to export the env without over-specific version numbers to make it machine un-specific? |
@soerendip there is a new flag in conda 4.7.12 that allows environments to be exported based on the history of what packages were explicitly requested (versions are only included if you explicitly specified a version when installing that package). Please try:
|
I believe you meant |
@forrestwaters |
https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html |
To sum up, working solution (without typo): |
Hi, I have tried your command line, but it still gave me such an error:
Any help would be appreciated, thanks! Sophia |
conda env export --no-builds > environment.yml ContinuumIO/anaconda-issues#9480 (comment)
For those who were still lost about this, I solved mine by importing the environment with Anaconda Navigator, it works :) |
The general idea is to make it work from |
I got this:
Problem solved by removing '=hdf63c60_6' in file environment.yaml from the original line |
To sum up, the following (as suggested above) still doesn't solve the issue for me:
Results in Note the same is true when trying to create the environment via
|
What do you mean in hear, could you expand your words for qutip? |
Hey guys, But there is still problem, that it doesnt create dokney environment from ubuntu.yml I have cloned donkeycar from git clone https://github.com/waveshare/donkeycar |
guys just ran in to the same problem, i realize that the anaconda installed from the GRAPHICAL installer works just fine, but if you export a yml file from the conda installed from graphical installer and use it at a conda installed from COMMAND LINE, it will run into this problem. updating conda/reinstalling it wouldn't help. |
…port --no-builds > env.yml to avoid ResolvePackageNotFound. See ContinuumIO/anaconda-issues#9480 for details
I exported an environment using
conda env export > environment.yml
.I installed miniconda3 on a different system, updated conda, installed pip.
Then
conda env create -f environment.yml -n py3
Actual Behavior
It gives me this error message:
Expected Behavior
The environment should be installed with the same packages indicated in the yml file. All necessary information, such as channels, should be provided by the yml file. And it should give a warning about packages from locally installed sources. I noted that e.g. the packages pyqsar from my source system is not available on the target system. Though conda did not raise a warning.
Steps to Reproduce
TARGET SYSTEM
environment.yml
The text was updated successfully, but these errors were encountered: