I do have conda installed locally and I can create environments natively in conda.
Is this install trying to go out to anaconda.com to retrieve packages? We cannot allow that and it is blocked.
All packages, etc have to be brought in securely, scanned and loaded in an internal repository.
How can we get these installations to work ?
Thank you very much for including the (rather hidden) conda log files.
The error “critical libmamba ssl_verify does not contain a valid file path.” points to an issue establishing a secure (https/SSL) connection, which falls in line with your statement on anaconda being blocked.
Our development team is aware of limitations relating to error reporting and is looking into both robustness improvements as well as documentation.
For the time being, you could try in a less restrictive network environment, or follow our guide for offline installations. This approach boils down to:
get the files you need on an unrestricted system
provide them to the restricted system(s) via a file share, USB stick, or similar.
I believe the Legacy Python for Python V2 is totally contained in the extension as downloaded from the KNIME extensions repository so it does not go back to the internet. It installs successfully for me too.
The newer packages appear to go to anaconda.com to download the actual packages at install time. We have package downloading from the internet blocked.
KNIME has some proposed solutions if you follow the suggestions above. They will not work on our site due to our security restrictions and practices.
At the moment for us, all Python in KNIME is unusable as well as any extensions that use Python.
We are not going to be allowed to have a KNIME workstation download packages unrestricted from the internet.
All packages are pulled and scanned by our security team and put in an internal repository for use by the employees.
We would need KNIME to specify exactly which packages are needed.
We would need to pull those packages and we would need to be able to point the KNIME extension installation process to use our internal repository.
Also, those packages have to be from pypi or the conda forge channel because Anaconda changed their commercial use licensing and we can only pull from the conda forge now.
At the moment, at least the way AP 5.2.2 is set up, we will not be able to support the use of Python in KNIME in our environment.
You’re on point, Steven. The new Python integration (and other pure-Python extensions, such as the Geospatial Analytics Extension) are not fully contained in update sites and will retrieve needed Python/Conda packages.
@Sebascun, the error “ShellExec command exited non-zero exit value” we display in the UI regrettably is a generic error that can have multiple causes. You will need to check the knime.log file for details (e.g. via Menu > Show KNIME log in File Explorer). However, common error causes are:
Restricted network access / proxies
File access issues (lacking write permissions, or a too long installation path on Windows)
Therefore, if possible, attempt an installation in an unrestricted network, and ensure that the KNIME installation is not installed in some very long path or enable long path support in Windows (personally, I’d recommend this to anyone, independent of KNIME).
@StevenLauretti, I’ll forwarded the package listing requirement to our development team. However, you can possibly already check the packages we need by going forward with the offline installation and inspecting the packages that are bundled by the unrestricted system, before moving them to the restricted system.
Hi Sebascu, had the same errormessage, and managed to fix the issue by replacing the “condarc” file under “C:\ProgramData\conda” with a near empty one containing only two lines:
“channels:”
“- defaults”
(without the quotation marks !)
That gave me the possiblity to install the “Knime Python Integration” extension.
