Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When the conda lock file is installed after mamba, mamba gets removed. #547

Merged
merged 2 commits into from
Jun 9, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,13 @@ RUN apt-get update && apt-get install -y \
# repository)
RUN git config --global --add safe.directory "${TASKS_MOUNT_DIR}"

# Create environments
RUN micromamba install -y -c conda-forge -n base conda mamba~=1.4.2

# Why are we copying these files to /tmp?
# TODO: Why are we copying these files to /tmp?
COPY --chown=$MAMBA_USER:$MAMBA_USER conda-lock.yml /tmp/conda-lock.yml
RUN micromamba install -y -n base -f /tmp/conda-lock.yml

# Install mamba. It is missing after installing `conda-lock.yml`
RUN micromamba install -y -c conda-forge -n base conda mamba~=1.4.2

COPY --chown=$MAMBA_USER:$MAMBA_USER environment.cmd.yml /tmp/environment.cmd.yml
RUN micromamba create -y -f /tmp/environment.cmd.yml
trey-stafford marked this conversation as resolved.
Show resolved Hide resolved

Expand Down