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

Option for packing without creating an archive #157

Closed
brglng opened this issue Dec 19, 2020 · 8 comments
Closed

Option for packing without creating an archive #157

brglng opened this issue Dec 19, 2020 · 8 comments
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability

Comments

@brglng
Copy link

brglng commented Dec 19, 2020

Hi Developers,

I would like to request a feature for providing an option for packing the environment to a directory, but not creating an archive. It would be nice if conda-pack could provide this feature. Thank you for your nice tool and greate work!

@brglng brglng changed the title [Feature Request] Option for packing without creating an archive Option for packing without creating an archive Dec 24, 2020
@LunarLanding
Copy link

LunarLanding commented Jan 30, 2021

I am interested in this too. I found conda-pack in a blog post about reducing image size for containers, and this compression-decompression is some overhead.
I read the code a bit and seems like a dummy Archiver class would work.
PS: I have moved to, in the container build script, installing conda, creating the environment I need and clearing unnecessary files. I think conda-pack use-case does not match mine.

@mcg1969 mcg1969 added the type::feature request for a new feature or capability label Feb 25, 2021
@mcg1969
Copy link
Contributor

mcg1969 commented Feb 25, 2021

This is an interesting point! Question: what would be the advantage of using a directory instead of, say, an uncompressed tar file?

@LunarLanding
Copy link

LunarLanding commented Feb 25, 2021

My reply above was in the context of making a script that would remotely build a container from an environment specification. Rather than understanding which parts of conda I could throw out to keep the environment working, I found conda-pack could do it for me. This was the silliest decision for my use case, because I don't need to move the environment to a different location, which makes activating the environment without conda simple enough (just change PATH, possibly run some scripts in activate.d) , and I'm not worried about depending on external repositories of packages. After all, if I ever feel like I need to freeze anything, I would freeze the container image.
As of now I'm using micromamba to install the environment. It's tiny so I don't even remove it from the container.

@brglng
Copy link
Author

brglng commented Feb 26, 2021

This is an interesting point! Question: what would be the advantage of using a directory instead of, say, an uncompressed tar file?

I use conda-pack for the packing and deployment of my Python service. My company's CI system requires putting all the files in a specific directory, and the system will then do the packaging. To meet the requirement, I have to use conda-pack to pack the environment and then unpack it to the directory. That's why I would like to have this feature, so that I would not have to do the packing-unpacking.

Thank you!

@ahirner
Copy link

ahirner commented Oct 9, 2021

We have the same use case as OP. Are there any objections against adding a --format folder option?

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Oct 10, 2022
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Nov 10, 2022
@moqmar
Copy link

moqmar commented Dec 8, 2022

As this is still more of a feature request, this is still relevant as of the current main branch.

@MLaurenceFournier
Copy link

As a user, I would like to add my vote for this feature. I was about to open a similar one.

At my workplace, we use conda-pack during the preparation of installers for our clients. Just after calling conda-pack, we extract the generated archive in a temporary folder. We then let the installer generation (Inno Setup in this case), re-archive the whole project including the packed (but extracted) python environment.

Having the "--format folder" option would simplify this use case.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Jun 20, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability
Projects
Archived in project
Development

No branches or pull requests

6 participants