Skip to content
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

Micromamba based setup? #75

Open
jaimergp opened this issue Sep 23, 2020 · 8 comments
Open

Micromamba based setup? #75

jaimergp opened this issue Sep 23, 2020 · 8 comments
Labels
type:enhancement New feature or request
Milestone

Comments

@jaimergp
Copy link
Member

Thoughts on this? https://github.com/mamba-org/mamba#micromamba

micromamba is a tiny version of the mamba package manager. It is a pure C++ package with a separate command line interface. It can be used to bootstrap environments (as an alternative to miniconda), but it's currently experimental. The benefit is that it's very tiny and does not come with a default version of Python.

It might be too soon because it's still experimental, but it could be helpful in the future.

@goanpeca
Copy link
Member

goanpeca commented Sep 23, 2020

Hi @jaimergp, thanks for the message.

See the discussion on #66. For now it seems the gains are not worth it, until MM is shipped with the container?

@mariusvniekerk
Copy link

So ensureconda (https://github.com/conda-incubator/ensureconda) is a tiny little tool that like pip ensures that a conda (or conda-like) is around.

It has some built in ways to install the standalone conda and micromamba. Generally not intended as a replacement for things like miniconda but more for conda related tools like conda-lock. Might suit some of your needs?

@mariusvniekerk
Copy link

We can certainly integrate some of the features from ensureconda into setup-miniconda if it makes sense

@goanpeca
Copy link
Member

Hi @mariusvniekerk thanks for it. I have been looking at ensure conda for some work I will be doing in constructor, so thanks for that.

The ideal place would be to have micromamba bundled with the github runners. Otherwise downloading things would be almost the same for the bundled miniconda (installing mamba) then downloading micromamba.

But to have things added to github runners (besides enough requests) is project maturity I think ?

@mariusvniekerk
Copy link

Yeah main difference is mostly the micromamba standalone installation doesn't need conda at all, so you save a conda solve for mamba.

@hadim
Copy link

hadim commented Nov 11, 2020

The "Setup Conda" step when used with mamba seems to take a long time without installing my custom deps only mamba-version to "*" (~6 min). A mamba only setup would probably fix this.

@goanpeca
Copy link
Member

The "Setup Conda" step when used with mamba seems to take a long time without installing my custom deps only mamba-version to "*" (~6 min). A mamba only setup would probably fix this.

Yep that is possible. Investigating these delays and trying to mitigate them.

@bollwyvl
Copy link
Contributor

Provided #126 goes through, this is ready for business, as in #76 (comment)

The difference here is that useMamba would need to get hoisted, earlier, and more forcefully, as no conda command would be available. It's also probably not a constructor-compatible CLI, but I could be wrong... if not, we'll need to do some updating in a few more places.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants