Minikube: ! VM is unable to access k8s.gcr.io, you may need to configure a proxy or set --image-repository

[rohit94j]

Hi there,

i am getting below error while executing minikube.exe start . Below is the complete output.

C:\Kubernetes>minikube.exe start

• minikube v1.8.2 on Microsoft Windows 10 Home Single Language 10.0.18362 Build 18362
• Automatically selected the virtualbox driver
• Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  ! VM is unable to access k8s.gcr.io, you may need to configure a proxy or set --image-repository
• Preparing Kubernetes v1.17.3 on Docker 19.03.6 ...
• Launching Kubernetes ...
• Enabling addons: default-storageclass, storage-provisioner
• Waiting for cluster to come online ...
• Done! kubectl is now configured to use "minikube"

[DasyDong]

same issue occurs on my mac

minikube version: v1.9.2

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/

[DasyDong]

issue occurs when using below commands:

 minikube start --docker-env HTTP_PROXY=xxx

When I run with splitting two steps , no error occurs

export HTTP_PROXY=xxx 
minikube start

[sharifelgamal]

@DasyDong yeah --docker-env is not going to do what you want it to, since you need HTTP_PROXY to be a local environment variable, not one inside the container runtime.

Our documentation (https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/) explicitly says exporting the environment variable is the correct idea. We'll fix the broken link in our output.

[sharifelgamal]

@rohit94j If you're behind a VPN or proxy, try looking at the link I linked above, otherwise try adding --image-repository=auto to your minikube start call.

[DasyDong]

@DasyDong yeah --docker-env is not going to do what you want it to, since you need HTTP_PROXY to be a local environment variable, not one inside the container runtime.

Our documentation (https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/) explicitly says exporting the environment variable is the correct idea. We'll fix the broken link in our output.

sounds good for me

[medyagh]

@rohit94j c@DasyDong do you still need help ?

Meanwhile have you tried out newest driver Docker Driver with latest version of minikube?
you could try
minikube delete
minikube start --driver=docker

for more information on the docker driver checkout:
https://minikube.sigs.k8s.io/docs/drivers/docker/

[sharifelgamal]

I'm going to go ahead and close this, feel free to reopen this if it remains an issue.

[nandrack]

Just starting learning k8s.
I still have this issue:
😄 minikube v1.15.1 on Fedora 33
✨ Automatically selected the docker driver
✅ Using image repository
👍 Starting control plane node minikube in cluster minikube
🔥 Creating docker container (CPUs=2, Memory=2200MB) ...
❗ This container 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/
🐳 Preparing Kubernetes v1.19.4 on Docker 19.03.13 ...
🔎 Verifying Kubernetes components...
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default