Use mamba to create devcontainer conda envs#704
Conversation
There was a problem hiding this comment.
It looks like as of #249 we are always making conda envs from scratch rather than updating. That being the case, can we narrow what's done conditionally here and merge more of the code paths for creating/updating? The comments are also a bit out of date relative to the current state of how it's working now.
There was a problem hiding this comment.
Yeah we always delete and recreate the env instead of updating it, because conda doesn't clean up after itself.
trxcllnt
left a comment
trxcllnt
left a comment
There was a problem hiding this comment.
Could you also bump the versions in the respective features' devcontainer-feature.json file?
|
Does mamba not respect the |
|
Ignoring |
trxcllnt
force-pushed
the
fix/use-mamba-env-create
branch
from
cb26471 to
872b0b9
Compare
3 participants
Description
Switch rapids-make-conda-env from
conda env create --solver=libmambatomamba env create.This keeps environment creation on mamba directly instead of invoking conda's env frontend with the libmamba solver.
Error outputs from mamba tend to be clearer, and it doesn't spam logs with a spinner like
- / | \ - / | \...