When I start the agent, asking it to use a specific docker image, I get the following messages (from the agent):

Executing Conda: /miniconda/condabin/conda install -p /root/.clearml/venvs-builds/3.10 -c pytorch -c conda-forge -c defaults -c pyg 'pip<20.2 ; python_version < '"'"'3.10'"'"'' 'pip<22.3 ; python_version >= '"'"'3.10'"'"'' --quiet --json
Conda error: DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment.
Use 'conda create' to convert the directory to a conda environment.
  target directory: /root/.clearml/venvs-builds/3.10

Local file not found [asttokens @ file:///home/conda/feedstock_root/build_artifacts/asttokens_1694046349000/work], references removed
Local file not found [backcall @ file:///home/conda/feedstock_root/build_artifacts/backcall_1592338393461/work], references removed
Local file not found [backports.functools-lru-cache @ file:///home/conda/feedstock_root/build_artifacts/backports.functools_lru_cache_1687772187254/work], references removed

From the above I can see/deduce the following:

• conda is trying to use the environments available in the agent machine that are mounted when the docker is started. Rightfully so, the system is complaining that /root/.clearml/venvs-builds/3.10 is not a conda environment...these are venv:s
• conda is looking for packages in /home/conda/feedstock: file:///home/conda/f which is not available in the docker image