I’m looking for a solution where environments do inherit from root, but searching for the answer there seems to be a lot of confusion. Many OP questions believe they are inheriting packages when they are not. So, the search results find these questions, but the answer has the counter solution (or just explain they are mistaken).
That said, one OP actually has a similar objective. Can packages be shared across Anaconda environments? This OP says they are running out of space on their HDD. The implication being “sharing” should use the same installed packages in the new environment. The answer (not accepted) is to use
I also found this post, Do newly created conda envs inherit all packages from the base env? which says
--clone does not share packages. In this post the OP believed their new environment “shared” packages, and then concludes “shared” packages don’t exist. What is the use of non-separated anaconda environments?
I tested both the
--clone flag, and the Conda Docs instructions to “build identical environments” options. Both env directories have the same identical size: 2G+. The only difference was building identical environment downloaded the packages again, and clone coppied the local file taking much less time.
I use Miniconda to deploy CLI tools to coworker workstations. Basically, the tools all use the same packages, with the occasional exception, when I need to add a particular module which I don’t want in the base install.