Creating envs (--conda-create-envs-only) is running without error, but not creating envs

[LLansing]

The following is my command and the output. No errors or warnings are shown, no new conda envs are shown with conda info --envs, and the command completes far faster than it would take to build any conda env.

$ atlas run all --use-conda --conda-create-envs-only [Atlas] INFO: Atlas version: 2.18.1 Config file //default_config.yaml is extended by additional config specified via the command line. DASTool uses the folowing binners: ['metabat', 'maxbin'] You have only one sample per bingroup. This doesn't use the co-abundance information. Building DAG of jobs... $

This had previously worked, but I've since recreated the atlasenv. Have conda environments been removed or changed in newer versions of ATLAS?

Atlas version 2.18.1

Additional context

[LLansing]

I believe I was mistaken - the conda environments that were built in previous run attempts seem to still be in my workspace, so subsequent runs seem to be using the conda envs just fine, despite having no connection to the internet.

My source of confusion is that these envs are not listed when running conda info --envs, but that, of course, is not a problem with ATLAS