From d7c26b7a79fb37be02228570f8e6660d3715cc75 Mon Sep 17 00:00:00 2001 From: Min RK Date: Wed, 3 Mar 2021 13:17:46 +0100 Subject: [PATCH] use mamba create instead of mamba env create I'm never sure what the difference is, but mamba env create doesn't accept explicit dependency format --- repo2docker/buildpacks/conda/install-miniforge.bash | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/repo2docker/buildpacks/conda/install-miniforge.bash b/repo2docker/buildpacks/conda/install-miniforge.bash index 5d3c5d9b..b5e0d051 100755 --- a/repo2docker/buildpacks/conda/install-miniforge.bash +++ b/repo2docker/buildpacks/conda/install-miniforge.bash @@ -46,7 +46,7 @@ time mamba install -y mamba==${MAMBA_VERSION} echo "installing notebook env:" cat /tmp/environment.yml -time mamba env create -p ${NB_PYTHON_PREFIX} -f /tmp/environment.yml +time mamba create --prefix ${NB_PYTHON_PREFIX} --file /tmp/environment.yml # empty conda history file, # which seems to result in some effective pinning of packages in the initial env, @@ -59,7 +59,7 @@ if [[ -f /tmp/kernel-environment.yml ]]; then echo "installing kernel env:" cat /tmp/kernel-environment.yml - time mamba env create -p ${KERNEL_PYTHON_PREFIX} -f /tmp/kernel-environment.yml + time mamba create --prefix ${KERNEL_PYTHON_PREFIX} --file /tmp/kernel-environment.yml ${KERNEL_PYTHON_PREFIX}/bin/ipython kernel install --prefix "${NB_PYTHON_PREFIX}" echo '' > ${KERNEL_PYTHON_PREFIX}/conda-meta/history mamba list -p ${KERNEL_PYTHON_PREFIX}