Remove exclusion of conda from clone command #14917
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
Currently conda as well as anything that depends on conda is exceluded when cloning an environment. This restriction is not needed, all packages including conda should be included in the cloning process.
Example:
(base) root@4d6e51d865c9:/# conda create --clone base --name target_env --yes
Source: /opt/conda
Destination: /opt/conda/envs/target_env
The following packages cannot be cloned out of the root environment:
- defaults/linux-64::conda-25.1.1-py312h06a4308_0
- defaults/linux-64::anaconda-anon-usage-0.5.0-py312hfc0e8ea_100
- defaults/noarch::conda-libmamba-solver-25.1.1-pyhd3eb1b0_0
- defaults/linux-64::conda-anaconda-telemetry-0.1.2-py312h06a4308_0
- defaults/linux-64::conda-anaconda-tos-0.1.2-py312h06a4308_0
Packages: 86
Files: 3
...
Downloading and Extracting Packages:
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
# $ conda activate target_env
#
# To deactivate an active environment, use
#
# $ conda deactivate
Why is this needed?
This would allow for cloning of the base environment for recovery or cloning a dev instance.
What should happen?
All packages including conda should be included in the cloning process.
Additional Context
No response