Reference base environment specifically in Quick Start install #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
Hi @shane-axiom, thanks for the PR! As you correctly indicated, this has been a bit of a pain point, so thanks for the useful suggestion. The examples in our |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few users have been tripped up when trying to install dependencies from environment files with specific environment names, which haven't been created.
#136
#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
namefor local usage, but to install that environment as thebaseenvironment when creating a portable Docker image using micromamba. I suspect there are others out there doing the same.Adding
-n baseto 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.