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

minikube cache add, doesn't add to other profiles unless restart #5974

Closed
medyagh opened this issue Nov 26, 2019 · 7 comments
Closed

minikube cache add, doesn't add to other profiles unless restart #5974

medyagh opened this issue Nov 26, 2019 · 7 comments
Labels
cmd/cache Issues with the "cache" command kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@medyagh
Copy link
Member

medyagh commented Nov 26, 2019

Here is how to reproduce:

start two minikube profiles

minikube start
minikube start -p p1

tag an image and add it to the cache

medya@~ $ docker tag alpine justforfun
medya@~ $ minikube cache add justforfun

ssh into minikube and see the images

medya@~ $ minikube ssh -p p1 docker images | grep justforfun
medya@~ $ minikube ssh -p minikube docker images | grep justforfun
justforfun                                latest              965ea09ff2eb        5 weeks ago         5.55MB

as we see the cached image was loaded to minikube profile but not p1

however if we restart p1, it will pick up the cached image

@medyagh medyagh added kind/bug Categorizes issue or PR as related to a bug. cmd/cache Issues with the "cache" command labels Nov 26, 2019
@medyagh
Copy link
Member Author

medyagh commented Nov 26, 2019

So the current behavior is, it loads image to the default profile without restart but for other profiles you need to restart.

What I suggest is this
Either

  • minikube cache add img, loads the image to all profiles

Or

  • minikube cache add be be bound to a profile only ! and if you add an image using this command only be lodaded from that profile (as opposed to to all profiles on restart)

What do you guys think?
@afbjorklund @tstromberg

@afbjorklund
Copy link
Collaborator

It's probably fine if it loads to the current profile only, but confusing if it does load to the others but isn't visible right away... That sounds like a bug, or at least something that was unintended ?

@medyagh
Copy link
Member Author

medyagh commented Dec 5, 2019

hm...for the PR I tried to keep the current behaviour.

@tstromberg
Copy link
Contributor

@medyagh - was this fixed?

@tstromberg tstromberg added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Dec 16, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 14, 2020
@sharifelgamal
Copy link
Collaborator

This is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmd/cache Issues with the "cache" command kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

6 participants