-
Notifications
You must be signed in to change notification settings - Fork 199
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
[optimize] add a new parameter to LoadOptions #1376
Comments
Hi @kakaZhou719, Thanks for reaching out and offering help, very much appreciated!
That sounds like a nice improvement assuming the user knows exactly the format of the archive. Before starting, I want to ask @mtrmac and @rhatdan what they think about your proposal. |
Fine with me. But I would like to hear from @mtrmac |
If this is for a new caller, I think a set of separate functions ( If this is for the primary |
@rhatdan @mtrmac @vrothberg ,thanks for your kind reply. BTW, could we support to set temporary directory when loading? the reason is that some image is very large, and require at least three times free disk to load. I see that current default temporary directory is the |
That’s configurable in c/image via |
Yes setting this in containers.conf, or setting the TMPDIR environment variable allow you to customize this. |
@rhatdan @mtrmac @vrothberg , do we have a plan to support a set of separate functions ( |
I would rather add a |
hi containers team,
when i learning our code, I found that If i knew the format of the tar file in advance , the program wouldn't need to guess the format, which will save a lot of time.
so , should we add a new parameter to indicate the format of load package on
LoadOptions
?FYI:
common/libimage/load.go
Line 33 in 28ebcc6
The text was updated successfully, but these errors were encountered: