-
Notifications
You must be signed in to change notification settings - Fork 2
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
envFile for devcontainer-features/micromamba => update base instead of create new env #25
Comments
Hi @nick-youngblut! Is this two separate issues?
|
Sorry, I got a bit lazy with this issue. It started out as a feature request, and then I noticed the potential bug. |
No worries, I was just a bit confused. I don't think the devcontainer feature can do much to work around the lack of Could you share your |
My
Thanks for your help! |
Hmm, we should be failing when the environment file isn't found. I'd make sure the We probably need better documentation. |
I'm pretty sure this ignores non-existent environment files without error. |
Ya, we probably want something like else
echo "ERROR (micromamba dev container feature): unable to find micromamba environment file ${ENV_FILE}"
exit 1
fi |
It would be great to just be able to update the base environment versus having to create a new conda env via
envFile
.It appears that micromamba does not include
micromamba env update
, unlikeconda
ormamba
.Moreover, I'm using:
in my devcontainer.json file, but the environment is not created, and there is no warning (e.g., "environment.yml file not found"). Running
micromamba env create -y -f environment.yml
runs successfully and creates the new environment.I'm using micromamba v1.5.6.
The text was updated successfully, but these errors were encountered: