-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Image load: Allow loading local images from tar or cache #10807
Conversation
Previously only allowed loading from daemon or remote via the cache, and not directly from local tarball.
They need to all be cached or all be local, though. If one appears to be local, then assume that all are.
@afbjorklund please rebase, so we could include in this release for end of march |
/ok-to-test |
@afbjorklund this pr does not change the behavior of Image Load to not load to all profiles, right ? Please clarify, (It would be great if our integration test would have covered it( |
kvm2 Driver Times for Minikube (PR 10807): 65.7s 66.6s 63.8s Averages Time Per Log
docker Driver Times for Minikube (PR 10807): 28.1s 28.1s 36.6s Averages Time Per Log
|
It is hardcoded to only load to the current profile. profile, err := config.LoadProfile(viper.GetString(config.ProfileName)) There are no changes to the "cache" commands, only renamed some internal functions. Added a "Cache" to the functions that wrap the cache dir, and Load does the load directly. |
kvm2 Driver Times for Minikube (PR 10807): 64.6s 66.1s 65.6s Averages Time Per Log
docker Driver Times for Minikube (PR 10807): 30.7s 27.8s 29.8s Averages Time Per Log
|
the cache related tests are failing
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it didn't fall back to remote correctly It was supposed to try the local daemon first, and if that fails then also try the remote registry. But make it possible to select which to try, and error out if not selecting any of the methods.... |
kvm2 Driver Times for Minikube (PR 10807): 66.5s 65.5s 64.5s Averages Time Per Log
docker Driver Times for Minikube (PR 10807): 31.3s 27.7s 28.3s Averages Time Per Log
|
@medyagh : There is also some bogus message about "cache" being replaced by "image load" ?
Even though image doesn't have any "memory". So you have to remember to load them again |
kvm2 Driver Times for Minikube (PR 10807): 64.8s 66.2s 65.7s Averages Time Per Log
docker Driver Times for Minikube (PR 10807): 29.2s 31.4s 34.3s Averages Time Per Log
|
yeah saw that, thats not very good, we gotta remove that |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund, medyagh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Now can load both from daemon/remote and from tarball:
To be on the safe side, one should use qualified names:
Also allows for loading more than one image at a time...
Closes #10744