Skip to content

Commit

Permalink
Reference base environment specifically in Quick Start install
Browse files Browse the repository at this point in the history
A few users have been tripped up when trying to install dependencies from environment files with specific environment names, which haven't been created.

mamba-org#136
mamba-org#151

This tripped me up for a minute as well. My workflow is pretty much always to have an environment.yml file with a non-base `name` for local usage, but to install that environment as the `base` environment when creating a portable Docker image using micromamba. I suspect there are others out there doing the same.

Adding `-n base` to the quick start install instructions both clarifies that we're installing to the base environment, and also allows installing into the base environment from environment files with embedded names by overriding the name.
  • Loading branch information
srstsavage committed May 17, 2022
1 parent b384b4c commit edd03ff
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ will install software into this 'base' environment.
```Dockerfile
FROM mambaorg/micromamba:0.23.2
COPY --chown=$MAMBA_USER:$MAMBA_USER env.yaml /tmp/env.yaml
RUN micromamba install -y -f /tmp/env.yaml && \
RUN micromamba install -y -n base -f /tmp/env.yaml && \
micromamba clean --all --yes
```

Expand Down

0 comments on commit edd03ff

Please sign in to comment.