Open epassaro opened 2 years ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Looks like there is some more recent discussion of this here: https://github.com/jupyterhub/repo2docker/issues/1312
Proposed change
Hi!
Conda currently supports exporting environments via
conda list --explicit > spec-file.txt
and installing them by doingconda create -n <env_name> --file spec-file.txt
.This kind of installation bypass the solver making builds really, really fast.
Alternative options
Also, using
mamba
instead ofconda
will speed up the deployment.Who would use this feature?
Conda environment users that wants to build their environments faster.
(Optional): Suggest a solution