-
Notifications
You must be signed in to change notification settings - Fork 221
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
create: always offer to pull #875
Conversation
Build succeeded.
|
Any feedback on this? |
Build failed.
|
So how about this |
Build failed.
|
An alternative for the pull part could be to make it an option instead: ie That would make it opt-in which should alleviate the storage space concerns with pulling newer images. Though in it's current form the user can already say "no" to downloading a newer image: they are prompted each time. |
Well, the best option would be to comment on containers/skopeo#641 and push for it to get prioritized. It's not entirely trivial to get the exact size of the image. |
Okay, sure, thank you for the detailed replies and clarity: let's drop the size part of this PR completely. (Actually I had not realized that skopeo was only exposing local image sizes.) |
Build failed.
|
Any hope of reviving this PR? It would vastly simplify the documentation on how to upgrade the Developer Toolbox I maintain, for instance. |
Build succeeded. ✔️ unit-test SUCCESS in 5m 33s |
I made my main branch current, which caused this PR to close - not that it was going anywhere... Anyway you can still find my original proposal in 8bfbbf4 in (https://github.com/juhp/toolbox/tree/always-pull) |
This PR addresses 2 common user issues with
toolbox create
:the hardcoded "500MB download" is misleadingI have tested this locally and it seems to work okay for me.