-
Notifications
You must be signed in to change notification settings - Fork 65
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
ENHANCMENT: save compressed subuser images #50
Comments
This is a good idea. I think, going off the example of git, we could call it |
Not sure if that would be the best for what I had in mind. Anyway, I implemented the first part of it to save to file: but will only send a pullrequest after the make image is merged. at the moment I live in Southamerica so I do not want to be always dependent on the internet even though it works mostly fine So my idea would be: Additional folder:
The compression is quite ok: the new This I already finished |
The second part I will do is a simple: command: the third part would be to integrate it into the normal subuser install procedure
Than it should first check if for any required dependency a saved image is available: this should work from top->bottom of dependencies because if a saved image for x11 is ready we do not need the lower dependent once Just an idea? |
maybe the list argument could also have an option |
the example: Anyway if we want we could add a compression level option: xz uses default level 6 of 9 |
compression level 9 did reduce a test image another 10+% libubuntu_precise compression6.tar.xz 36.2MB |
I will work on going over all your comments tomorrow. It's 1 am here, and I want to think this through properly... |
This feature needs to be better thought out. How is the user expected to restore these saved images? Also, creating a new top level directory for every feature is a no-go, it polutes the directory tree making it harder for the user to orient themselves in the sourcecode. What exactly is the goal of this feature? Is the user then going to copy the entire subuser directory over to another machine and type some command like "subuser install-from-saved-images"? I don't understand the user interface that is expected here... Tim
see explanation: 47e3647#commitcomment-5405340 |
It just occured to me, that putting the image-id into the filename won't work on Windows due to the 255 character long path restriction. |
I think that we shouldn't worry about that though. Some advanced features may not be supported on outdated operating systems ;) |
Do you want an image file and a extra jsonlike
firefox-image.json has the output of inspect |
That would be fine. But don't put the program name in the name of the files. It is simpler to progam if the names are standard. |
hi, |
Before starting with subuser a couple of days ago I looked into saving compressed docker images to file.
Because I like to be as much as possible internet independent (or if one uses subuser with a slower connection on a mobile ect.. or download limit) I will add the option to save subuser program images to file.
build once transfer and install multiple times.
The text was updated successfully, but these errors were encountered: