ARTIFACTORY: Pulling Packages from Conda using other channels as conda-Forge into Artifactory

ARTIFACTORY: Pulling Packages from Conda using other channels as conda-Forge into Artifactory

AuthorFullName__c
Bassel Mbariky
articleNumber
000005821
FirstPublishedDate
2023-07-17T17:26:45Z
lastModifiedDate
2025-07-20
VersionNumber
2

To successfully pull packages from a separate Conda channel such as conda-forge into Artifactory, you can follow the steps outlined below:

     1. Configure Artifactory to work with conda-forge by setting up a remote Conda repository with the following URL: 

https://conda.anaconda.org/conda-forge

User-added image

2. You can obtain the configuration details from the Artifactory UI using the Set Me Up section, as shown in the picture below. Here is an example of how the .condarc file might look:
channel_alias: http://<USER>:<API_KEY>@<JFROG_URL>/artifactory/api/conda/<REPO_NAME>;;
channels:
  -  http://<USER>:<API_KEY>@<JFROG_URL>/artifactory/api/conda/<REPO_NAME>;;

default_channels:
  -  http://<USER>:<API_KEY>@<JFROG_URL>/artifactory/api/conda/<REPO_NAME>;;

User-added image

Install the desired package from conda-forge using the following command:
"conda install  zipp"

If you encounter any proxy-related issues, please refer to the documentation for guidance on managing the proxy. Additionally, an alternative approach is to utilize the NO_PROXY environment variable, which allows you to exclude specific interfaces, IPs, and addresses from the default proxy configuration. The documentation provides detailed information on implementing this approach effectively.

By following these steps, you will be able to successfully pull packages from the conda-forge channel into Artifactory.