-
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
How to update the conda base environment? #55
Comments
Also, what about using micromamba instead of miniconda? |
There is no automated procedure for updating the base environment. Its outside of the containerisation anyway, so updating it would just follow the standard procedure for updating a conda env. Micromamba looks interesting, I had no idea it existed. I'd gladly replace a base conda environment with micromamba, but I'd a) alias the 'conda' command to it and b) make sure that it does everything users need the 'conda' command to do. That way, users can follow external conda docs and everything should work as expected. |
I am really struggling with the deployment of a conda environment that includes esmvaltool, ilamb etc... |
Hmmm... The idea behind this setup was that the base conda installation would happen once per system, and any environments would be built on top of that. I can see the issue around versioning though, I guess it doesn't cope when you change it to build an 'ilamb-0.1' or 'esmvaltool-0.1' environment. I think that'd be a good feature to implement, maybe separating out different environment classes under the 'scripts' directory and separating out I probably won't be in this week, but I'm happy to tee up something for next week. I'll ping you on slack and we can discuss further. |
Hi @rbeucher. Reviving this issue as I took advantage of the January quiet time to revisit ways to handle creation and maintenance of different environments. This is the result of that. I've also switched it to micromamba, which worked great apart from compatibility with I'm planning to do the switchover on launch of the analysis-24.01 environment, which will be towards the end of next week. With any luck, users won't notice the change and I can quietly delete the entire conda base environment after a little while. Thanks for the discussion, and for raising this issue in the first place! |
Hi @dsroberts, Thanks! That looks great. I am going to have a look and will let you know how it goes. Thanks for sharing! |
Completed in #64 |
Hi,
I am struggling a bit, trying to get a new environment deployed. For some reasons, it works on my local machine. Mamba can solve the environment and install it.
I was gonna try to update the conda base environment but I am not sure how to do that without breaking things.
@dsroberts can you help?
R
The text was updated successfully, but these errors were encountered: