By using AWS re:Post, you agree to the Terms of Use

Not able to clone a conda environment on deep learning amis

0

I am trying to clone a conda tensorflow environment in EC2 instance, but I am unable to do so. I need this as I am installing some libraries that are not compatible with the my current environment. I have a working environment now and I want to keep it to run other experiments while I meddle within the cloned version and new library installations. I get below errors while trying to clone

conda create --name tensorflow2_p38_clone --clone tensorflow2_p38

Source:      /home/ubuntu/anaconda3/envs/tensorflow2_p38
Destination: /home/ubuntu/anaconda3/envs/tensorflow2_p38_clone
Packages: 445
Files: 53101
Preparing transaction: done
Verifying transaction: /
SafetyError: The package for nb_conda located at /home/ubuntu/anaconda3/pkgs/nb_conda-2.2.1-py38h578d9bd_4
appears to be corrupted. The path 'lib/python3.8/site-packages/nb_conda/envmanager.py'
has an incorrect size.
  reported size: 6179 bytes
  actual size: 6209 bytes

ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'bin/sip'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'include/python3.8/sip.h'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'lib/python3.8/site-packages/__pycache__/sipconfig.cpython-38.pyc'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'lib/python3.8/site-packages/__pycache__/sipdistutils.cpython-38.pyc'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'lib/python3.8/site-packages/sipconfig.py'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::pyqt5-sip-4.19.18-py38h709712a_8, conda-forge/linux-64::sip-4.19.25-py38h709712a_1
  path: 'lib/python3.8/site-packages/sipdistutils.py'


ClobberError: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/noarch::jupyter_client-7.0.6-pyhd8ed1ab_0, conda-forge/noarch::nbclient-0.5.8-pyhd8ed1ab_0
  path: 'bin/jupyter-run'

                                                                                                                      done
Executing transaction: |
For Linux 64, Open MPI is built with CUDA awareness but this support is disabled by default.
To enable it, please set the environment variable OMPI_MCA_opal_cuda_support=true before
launching your MPI processes. Equivalently, you can set the MCA parameter in the command line:
mpiexec --mca opal_cuda_support 1 ...

In addition, the UCX support is also built but disabled by default.
To enable it, first install UCX (conda install -c conda-forge ucx). Then, set the environment
variables OMPI_MCA_pml="ucx" OMPI_MCA_osc="ucx" before launching your MPI processes.
Equivalently, you can set the MCA parameters in the command line:
mpiexec --mca pml ucx --mca osc ucx ...
Note that you might also need to set UCX_MEMTYPE_CACHE=n for CUDA awareness via UCX.
Please consult UCX's documentation for detail.

                                                                                                                      - Config option `kernel_spec_manager_class` not recognized by `EnableNBExtensionApp`.
Enabling notebook extension jupyter-js-widgets/extension...
      - Validating: OK
                                                                                                                      \ Enabling nb_conda_kernels...
CONDA_PREFIX: /home/ubuntu/anaconda3/envs/tensorflow2_p38_clone
Status: enabled
                                                                                                                      / Config option `kernel_spec_manager_class` not recognized by `EnableNBExtensionApp`.
Enabling notebook extension nb_conda/main...
      - Validating: OK
Enabling tree extension nb_conda/tree...
      - Validating: OK
Config option `kernel_spec_manager_class` not recognized by `EnableServerExtensionApp`.
Enabling: nb_conda
- Writing config: /home/ubuntu/anaconda3/envs/tensorflow2_p38_clone/etc/jupyter
    - Validating...
      nb_conda 2.2.1 OK

I had the same issue previously on different EC2 instance as well which I ignored at the time

No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions