-
Notifications
You must be signed in to change notification settings - Fork 88
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
Make conda/mamba flavor a build arg #489
Comments
Maybe just start with the official base images instead of duplicating config? |
Sure, we could do something like this instead: holzman@c2c54e0. One downside - since the base image is bigger, the derived image is larger by about 130 MB. |
I'd like to avoid changing the base image, it includes too much potential unwanted consequences etc. I think providing a configurable arg is reasonable if needed, but I'd like some clarity about the reason to change you describe.
Do you have a reference to this? |
(I am not a lawyer...) Conda and the anaconda installers are wholly free and open source. However, use of the anaconda repository is only unlimited free for certain categories, and enterprises may be required to purchase Commercial Edition or other product. Note that (mini-, micro-...)mamba uses the same repos as conda, and that conda-forge's repo data and metadata are hosted by anaconda, so the terms are (I think) the same. |
The licensing change dates from 2020 (https://www.anaconda.com/blog/sustaining-our-stewardship-of-the-open-source-data-science-community). Recently, anaconda.org decided that my organization - Fermilab - which is a 501(c)(3) research institution - fell under "commercial activities" and would require purchasing licenses to use the default channels. @martindurant: The default channel is not unlimited/free, but conda-forge is: https://conda-forge.org/blog/posts/2020-11-20-anaconda-tos/ |
Hm, OK then I suppose I am confused too, along with everyone else. None of the open source projects I am connected with (some without any anaconda involvement) seems to have a problem. Obviously, I have no idea how it is decided whether a organisation counts as commercial or not. I would be happy to ask. |
@consideRatio: Hopefully that's enough justification for this change? I didn't know if you need more detail on Fermilab and Anaconda. |
@holzman in #533 I'm proposing to change the image significantly, which involves installing a more primitive image and encourage users to maintain their own image for the scheduler and worker pods when creating clusters via dask-gateway installed with a helm chart. This project has a need for maintenance sustainability, this is a proper step in that direction. Like this, you end up responsible for building an image for your scheduler/worker pods. I'm curious to hear what do you think about this @holzman, it is always tricky to balance things when maintaining open source projects and I think your input could be helpful for this balance! |
I know there was some discussion of using mamba in #432. Due to the change in anaconda.org's licensing agreements, we prefer to use miniforge/mambaforge whenever possible.
A patch like this: holzman@96b7145 seems like it should make everyone happy.
The text was updated successfully, but these errors were encountered: