AnsweredAssumed Answered

Create cloned conda environment as user

Question asked by curtvprice

on Jun 14, 2017
Latest reply on Jul 9, 2018 by PSLarkin_SpokaneCounty

Like • Show 0 Likes0
Comment • 18

I am not allowed admin access, but I really want to be able to use pro's Conda environment. Currently my only option is to run another Conda install, but in theory, can't I clone the Pro environment to a folder have access to?

Conda suggests this:

Error: Missing write permissions in: C:\ArcGIS\Pro\bin\Python
#
# You don't appear to have the necessary permissions to update packages
# into the install area 'C:\ArcGIS\Pro\bin\Python'.
# However you can clone this environment into your home directory and
# then make changes to it.
# This may be done using the command:
#
# $ conda create -n my_arcgispro-py3 --clone=C:\ArcGIS\Pro\bin\Python\envs\arcgispro-py3

but if I try it I get an error message:

PermissionError: [WinError 5] Access is denied: 'C:\\ArcGIS\\Pro\\bin\\Python\\nvs\\my_arcgispro-py3'

Is this possible?

CDow-esristaff

Jun 14, 2017 1:09 PM

Correct Answer

Currently it's not supported, we are moving towards enabling that sort of environment creation as soon as possible but there has been a lot to change behind the scenes, since many different parts of Pro use Python in different ways. Currently the env needs to be within the Pro folder structure to find all the pyd/DLL files that arcpy needs to initialize. If all goes according to plan this should be fixed for 2.1.

Currently you can use the 'prefix' switch on conda create (-p) to clone the env somewhere outside the Pro folder structure, but will have to ensure the system PATH variable includes all of the locations of the DLLs to successfully import arcpy, but its not something we're officially supporting since its a bit of a hack.

See the reply in context

No one else had this question

Outcomes

18 Replies

CDow-esristaff Jun 14, 2017 1:09 PM
Unmark Correct
Correct Answer
Currently it's not supported, we are moving towards enabling that sort of environment creation as soon as possible but there has been a lot to change behind the scenes, since many different parts of Pro use Python in different ways. Currently the env needs to be within the Pro folder structure to find all the pyd/DLL files that arcpy needs to initialize. If all goes according to plan this should be fixed for 2.1.

Currently you can use the 'prefix' switch on conda create (-p) to clone the env somewhere outside the Pro folder structure, but will have to ensure the system PATH variable includes all of the locations of the DLLs to successfully import arcpy, but its not something we're officially supporting since its a bit of a hack.
5 people found this helpful
Like • Show 0 Likes0
Actions
- curtvprice @ CDow-esristaff on Jun 14, 2017 1:33 PM
  Mark Correct
  Correct Answer
  Clinton, thanks so much for the clear answer, really appreciate it!
  Like • Show 0 Likes0
  Actions
- tobiasli @ CDow-esristaff on Aug 7, 2017 1:57 AM
  Mark Correct
  Correct Answer
  Hello Clinton,
  
  Our organization uses python 3.4 for all business applications. So I obviously use the arcpy supplied with ArcGIS Pro for scripts and tools that need both GIS-functionality and access to business data. As part of this, I need to be able to access arcpy from external python environments, as we use a custom anaconda server to distribute all our api's, and this cannot be installed with ArcGIS Pro's environment.
  
  So I was very surprised after I upgraded to ArcGIS Pro 2.0 that this feature that was external environment access was revoked. I can no longer access arcpy from outside of ArcGIS Pro. I will have to downgrade until a solution is found.
  
  You say that there is a hack, but I cannot find information regarding this anywhere.
  Like • Show 0 Likes0
  Actions
  - CDow-esristaff @ tobiasli on Aug 9, 2017 9:36 AM
    Mark Correct
    Correct Answer
    Hi Tobias,
    
    You can edit the .condarc file in %ProInstall%/bin/Python to include more than the default channels/servers which are supported on a base installation, to install packages hosted on your servers. This should allow you to install the packages into Pro environments.
    
    We are working on packaging arcpy for the next release of Pro to ensure it can be used anywhere on a system with the application installed. For now the workaround is ensuring the PATH (both sys.path and os.environ['PATH']) in your system conda install matches that in the Pro conda environments, which should provide arcpy with the binary files it needs to instantiate.
    2 people found this helpful
    Like • Show 1 Like1
    Actions
    - Dan_Patterson @ CDow-esristaff on Aug 9, 2017 5:47 PM
      Mark Correct
      Correct Answer
      An FYI for those that will be disappointed if they examine their condarc files
      Configuration- Conda
      Like • Show 1 Like1
      Actions
      - CDow-esristaff @ Dan_Patterson on Aug 10, 2017 12:08 PM
        Mark Correct
        Correct Answer
        We did evaluate adding more to the .condarc file but for every option there are potential edge cases which could be problematic, so figured it was a good idea to adhere to the minimal .condarc that comes with a base conda installation.
        3 people found this helpful
        Like • Show 0 Likes0
        Actions
        Dan_Patterson @ CDow-esristaff on Aug 10, 2017 12:23 PM
        Mark Correct
        Correct Answer
        I suspected as much Clinton...(since the 2 liner .condarc paled in comparison to the sys and os path info )
        It would be interesting to see some of the options that were considered, but I guess I will just experiment on my own configuration since I use local everything and work local
        Like • Show 1 Like1
        Actions
    - tobiasli @ CDow-esristaff on Sep 25, 2017 1:27 AM
      Mark Correct
      Correct Answer
      Thanks for the reply Clinton Dow,
      
      When I edit the .condarc-file, I would expect the list of available packages in the ArcGIS Pro Python Package Manager to change, reflecting the packages available in the new conda-sources.
      
      What I've done is change the C:\Program Files\ArcGIS\Pro\bin\Python\.condarc - file with the following iterations:
      Original:
      channels: - esri - default
      New 1:
      channels: - esri - defaults - http://anaconda:8080/conda/company
      New 2:
      channels: - esri - http://anaconda:8080/conda/company
      New 3:
      channels: - http://anaconda:8080/conda/company
      New 4:
      channels:
      I check the contents of ArcGIS Pro => Projects => Python => Add packages after editing .condarc:
      - None of the above condarc-files show any of the packages hosted on our anaconda server.
      - Even with a completely empty .condarc-file (New 4), nothing changes in ArcGIS Pro in the list of available packages.
      
      So I'm not sure how ArcGIS Pro uses the references in the .condarc-file.
      
      I also have the company approved Miniconda installed on my machine, and that conda instance is the machine default. But ArcGIS Pro is not using this by mistake, as our Miniconda is configured to solely (and successfully) communicate with our in-house anaconda server at http://anaconda:8080/conda/company.
      
      I would like to interact with ArcGIS Pro's conda via the command line to figure out whats going on, but I can't figure out how. Do you have any tips?
      
      I might mention that I'm also communicating with my local Esri distributor about this issue as well, but without any luck.
      
      The documentation for Pro and Conda seems to only cover interaction via ArcGIS Pro GUI:
      The Python Package Manager—ArcPy Get Started | ArcGIS Desktop
      Like • Show 0 Likes0
      Actions
      - CDow-esristaff @ tobiasli on Sep 25, 2017 9:54 AM
        Mark Correct
        Correct Answer
        Hello Tobias,
        
        Once you have added the new channel you still have to refresh conda's metadata, its done automatically before conda runs most commands on the command line or clicking the blue circular arrow button in the UI. We ran into some complications with the metadata json files due to UAC when installed in Program Files so that experience will be improved going forward.
        
        The conda executable that Pro is using is within the %ProInstall%/bin/Python/Scripts directory, so you can work with conda via the command line if its on your PATH. Alternatively there is a batch file which should be in the start menu in the ArcGIS program group under 'Python Command Prompt' which will open to the environment's location and activate it for you.
        
        Hope that helps get you in the right direction!
        2 people found this helpful
        Like • Show 0 Likes0
        Actions
        tobiasli @ CDow-esristaff on Sep 26, 2017 12:07 AM
        Mark Correct
        Correct Answer
        Ok, great! That worked.
        
        Thank you very much, Clinton Dow. You have been ever so helpful.
        Like • Show 1 Like1
        Actions
- gisspellblade @ CDow-esristaff on Jun 25, 2018 11:28 AM
  Mark Correct
  Correct Answer
  Has the creation of new environments been address yet in Pro?
  Like • Show 1 Like1
  Actions
  - CDow-esristaff @ gisspellblade on Jun 27, 2018 12:01 PM
    Mark Correct
    Correct Answer
    Yes, new environments will now go to the user's AppData/Esri/conda directory which should allow them to interact with it and not experience permission issues.
    2 people found this helpful
    Like • Show 1 Like1
    Actions
    - curtvprice @ CDow-esristaff on Jun 27, 2018 2:53 PM
      Mark Correct
      Correct Answer
      Is this the case for per-user installs of ArcGIS Pro? Or admin installs too?
      Like • Show 0 Likes0
      Actions
- PSLarkin_SpokaneCounty @ CDow-esristaff on Jun 27, 2018 11:48 AM
  Mark Correct
  Correct Answer
  Any update? It doesn't appear supported in 2.2
  Like • Show 0 Likes0
  Actions
  - CDow-esristaff @ PSLarkin_SpokaneCounty on Jun 27, 2018 11:59 AM
    Mark Correct
    Correct Answer
    You should now be able to clone environments in 2.2 via the Manage Environments dialog by selecting an environment and clicking the clone button to the right hand side.
    Like • Show 0 Likes0
    Actions
    - PSLarkin_SpokaneCounty @ CDow-esristaff on Jun 27, 2018 1:01 PM
      Mark Correct
      Correct Answer
      Thanks for your reply.
      
      Is it possible to clone the acrgis pro environment outside of the Pro root directory? For production level processes/analysis it is risky to rely on code in user folders. It is actually impossible most cases for me to run after hours processes and have access to my user folder.
      Like • Show 0 Likes0
      Actions
      - Hakon.Dreyergeodata-no-esridist @ PSLarkin_SpokaneCounty on Jul 4, 2018 7:31 AM
        Mark Correct
        Correct Answer
        This is possible using conda from the Python Command Prompt. From there you may clone environments to your chosen location.
        conda create --clone arcgispro-py3 --prefix c:\mydir\myclone
        note that if you put your environment outside the defined envs directories they will not be listed using
        conda info --envs
        But you may still activate the environment, and all conda functionality are available, but you must use full path to the environment. Set active:
        activate c:\mydir\myclone
        Or just reference the clone with a full path when running conda commands:
        conda install --name c:\mydir\myclone flask
        
        NB: At the moment you may hit the issue described here https://community.esri.com/thread/217048-arcgis-pro-220-and-python-package-manager?sr=inbox&ru=159379 but I guess there will be a fix out soon.
        2 people found this helpful
        Like • Show 0 Likes0
        Actions
        PSLarkin_SpokaneCounty @ Hakon.Dreyergeodata-no-esridist on Jul 9, 2018 11:39 AM
        Mark Correct
        Correct Answer
        Thanks for your help. I was able to clone an environment outside of the pro directory and import arcpy from python from that env.
        
        I think I'll wait for Pro 2.2.1. While I can't recreate the bug at 2.2 I'd rather not risk it.
        1 person found this helpful
        Like • Show 1 Like1
        Actions

GeoNet

The Esri Community

Create cloned conda environment as user

Outcomes

Related Content

Recommended Content

Incoming Links