Minikube: kubeadm with None driver deletes other local docker images
The minikube 0.26.0 was installed successfully. But there is a serious problem. On my ubuntu 16.04 virtualbox vm, I have pulled k8s images for minikube dashboard. After running sudo -E minikube start --vm-driver=none, all the docker images including my private images such as hyperledger fabric are deleted without any notification!!
bh4rtp
All 14 comments
the docker images are deleted when running minikube dashboard, not minikube start.
bh4rtp
on 11 Apr 2018
Yeah I had something like this as well, except it's not when you start dashboard or start Minikube.
I reverted to 0.25 and everything went back to normal.
antonyisoardi
on 13 Apr 2018
i am using 0.25.0. yesterday, all my local docker images were deleted too. feel strange.
bh4rtp
on 10 May 2018
I am also seeing this, although I'm using minikube V0.28.0. Any update on this issue?
muthmano-dev
on 19 Jun 2018
My guess is that this is the kubelet image garbage collector. It's probably unavoidable when using the none driver - the kubelet assumes full control over the machine and docker daemon.
dlorenc
on 19 Jun 2018
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
fejta-bot
on 17 Sep 2018
It would be nice if kubeadm, or at least ourselves, could detect this possibility and prompt the user rather than quietly deleting everything.
tstromberg
on 19 Sep 2018
Can we interact with https://github.com/kubernetes/kubernetes/issues/68930 to find a solution?
bhack
on 10 Oct 2018
It would be nice if kubeadm, or at least ourselves, could detect this possibility and prompt the user rather than quietly deleting everything.
we add some code in kubelet that user can specify a list of image that garbage will ignore here
maybe it can fix this
https://github.com/kubernetes/kubernetes/pull/68549
zhangmingld
on 15 Oct 2018
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
fejta-bot
on 14 Nov 2018
Don't stale this
bhack
on 14 Nov 2018
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 14 Dec 2018
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
k8s-ci-robot
on 14 Dec 2018
FWIW, If this was indeed caused by the kubelet reaping disk space, I believe this was fixed by #3671 - which is part of minikube v0.34.0. If this is not the case, please re-open. Thanks!
tstromberg
on 16 Feb 2019
Related issues
StasPerekrestov
路
3Comments
jroucheton
路
3Comments
alber70g
路
3Comments
wudongyin
路
3Comments
olalonde
路
3Comments
Most helpful comment
FWIW, If this was indeed caused by the kubelet reaping disk space, I believe this was fixed by #3671 - which is part of minikube v0.34.0. If this is not the case, please re-open. Thanks!