Closed peterlin741 closed 4 years ago
As best as I can tell, minikube and Kubernetes are running just fine, though the docker errors are interesting. I'm having a difficult time following along on how to replicate the error though.
If I attempt to run an application (cloud run) that starts a gcloud managed version of minkube (v1.7.3), while a local version of minikube (v1.8.2) is running and set as the current context, the sample fails and corrupts the state of docker.
Are you seeing something else other than docker errors?
My best guess as to what may be happening is that something may be caching the Docker IP and port returned by minikube, but some external environment is changing that. If you see the docker error again, can you share the output of:
minikube docker-env -p <environment>
eval $(minikube docker-env -p <environment>) && docker version
Thanks for the report!
Will retest when the new version of gcloud is released (pointing at the latest minikube)
have you bumped into this again?
I haven't seen this exact issue recently (managed version on v1.8.2
), although whenever minikube gets stuck, restarting docker and running minikube delete
fixes it.
Our team will be doing further testing this week, so I'll comment here if the issue shows up again when using the latest version of minikube.
@peterlin741 - "whenever minikube gets stuck" sounds bad. Do you mind opening an issue about that? It shouldn't happen regularly at all. I would love to get --alsologtostderr
output from a case where it occurs.
We've talked about offering a flag to automatically restart stuck Docker daemons, but it seems a bit invasive to do by default.
@peterlin741 - "whenever minikube gets stuck" sounds bad. Do you mind opening an issue about that? It shouldn't happen regularly at all. I would love to get
--alsologtostderr
output from a case where it occurs.We've talked about offering a flag to automatically restart stuck Docker daemons, but it seems a bit invasive to do by default.
Sure, I can open an issue if I see it again and include the logs
If I attempt to run an application (cloud run) that starts a gcloud managed version of minkube (
v1.7.3
), while a local version of minikube (v1.8.2
) is running and set as the current context, the sample fails and corrupts the state of docker. (other scenarios may fail as well)Afterwards, if I switch to a different context (a gke cluster for example) and/or if I do a
minikube delete
and remove my local version of minikube from the kubectl context, the gcloud managed version of minikube somtimes still may not be able to start through IntelliJ, when running the sample. (what a normal user would try)However, after deleting both minikube contexts, running
minikube delete --all --purge
, and restarting docker, rerunning the sample locally is able to work.The exact command to reproduce the issue
minikube start --profile cloud-code-minikube --keep-context true --wait false --vm-driver docker --interactive false --alsologtostderr -v=8
, which is run from my applicationHere are some of the docker errors
The full output of the command that failed (mixed in with application specific logs):
The output of the
minikube logs
command:The operating system version: macOS 10.15.3