Closed cmeans closed 4 years ago
Found some help on the minikube slack. Now using:
minikube start --driver=docker
And it's working for me. However, it is slower...so would like a better solution, but am functional at the moment. OK, to close if you prefer.
@cmeans I am curious what was the driver you were using before docker ? And also could your slower experience be because your docker has a lot of abandoned images ?
Could you try to prune your docker images and see if that makes it better ?
@medyagh I was not specifying a driver before. In the time I've been using Minikube, which is only a few weeks now, I believe the default may have changed.
I have pruned recently (necessary to deal with another issue), but will try that again (and maybe shut down Folding@Home as well :) ).
@medyagh Hyperkit
@cmeans if u are on VPN i reocmmend using our docker driver instead of hyperkit. and for pushing images, have seen this docs ? https://minikube.sigs.k8s.io/docs/handbook/pushing/
does that answer your quesiton?
@cmeans did using docker driver help ?
I haven't heard back from you, I wonder if you still have this issue? Regrettably, there isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.
I will close this issue for now but please feel free to reopen whenever you feel ready to provide more information.
Sorry...still having the issue, but we've ditched trying to use minikube for the moment, and will live with docker-compose only. I will revisit once docker-compose is insufficient for our needs.
Steps to reproduce the issue:
Full output of failed command: Sending build context to Docker daemon 126.4MB Step 1/12 : FROM ruby:2.5.7 Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Full output of
minikube start
command used, if not already included: ā³ $ minikube start š minikube v1.9.2 on Darwin 10.15.4 āØ Using the hyperkit driver based on existing profile š Starting control plane node m01 in cluster minikube š Restarting existing hyperkit VM for "minikube" ... š³ Preparing Kubernetes v1.18.0 on Docker 19.03.8 ... ā This VM is having trouble accessing https://k8s.gcr.io š” To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/ š Enabling addons: dashboard, default-storageclass, ingress, ingress-dns, registry, storage-provisioner š Done! kubectl is now configured to use "minikube"Optional: Full output of
minikube logs
command: