Minishift start fails because of unable to pull images from docker registry

[anjannath]

General information

• Minishift version: master
• OS: Linux / macOS / Windows (all)

Steps to reproduce

1. minishift start

Expected

minishift start complete successfully and deploys an OpenShift 3.11 cluster

Actual

minishift start fails with the following error, minishift start -v5 will show the error from docker

❯ minishift start -- Starting profile 'minishift' -- Check if deprecated options are used ... OK -- Checking if https://github.com is reachable ... OK -- Checking if requested OpenShift version 'v3.11.0' is valid ... OK -- Checking if requested OpenShift version 'v3.11.0' is supported ... OK -- Checking if requested hypervisor 'kvm' is supported on this platform ... OK -- Checking if KVM driver is installed ... Driver is available at /usr/local/bin/docker-machine-driver-kvm ... Checking driver binary is executable ... OK -- Checking if Libvirt is installed ... OK -- Checking if Libvirt default network is present ... OK -- Checking if Libvirt default network is active ... OK -- Checking the ISO URL ... OK -- Checking if provided oc flags are supported ... OK -- Starting the OpenShift cluster using 'kvm' hypervisor ... -- Minishift VM will be configured with ... Memory: 4 GB vCPUs : 2 Disk size: 20 GB -- Starting Minishift VM .................. OK -- Checking for IP address ... OK -- Checking for nameservers ... OK -- Checking if external host is reachable from the Minishift VM ... Pinging 8.8.8.8 ... OK -- Checking HTTP connectivity from the VM ... Retrieving http://minishift.io/index.html ... OK -- Checking if persistent storage volume is mounted ... OK -- Checking available disk space ... 1% used OK -- Writing current configuration for static assignment of IP address ... WARN Importing 'openshift/origin-control-plane:v3.11.0' .............. OK Importing 'openshift/origin-docker-registry:v3.11.0' ....... OK Importing 'openshift/origin-haproxy-router:v3.11.0' ...... OK -- OpenShift cluster will be configured with ... Version: v3.11.0 -- Copying oc binary from the OpenShift container image to VM ... OK -- Starting OpenShift cluster ..Error during 'cluster up' execution: Error starting the cluster. ssh command error: command : /var/lib/minishift/bin/oc cluster up --routing-suffix 192.168.42.95.nip.io --base-dir /var/lib/minishift/base --image 'openshift/origin-${component}:v3.11.0' --public-hostname 192.168.42.95 err : exit status 1 output : Getting a Docker client ... Checking if image openshift/origin-control-plane:v3.11.0 is available ... Pulling image openshift/origin-cli:v3.11.0 E0423 12:16:24.747811 2205 helper.go:173] Reading docker config from /home/docker/.docker/config.json failed: open /home/docker/.docker/config.json: no such file or directory, will attempt to pull image docker.io/openshift/origin-cli:v3.11.0 anonymously error: error pulling Docker image openshift/origin-cli:v3.11.0

❯ minishift ssh [docker@minishift ~]$ docker pull openshift/origin-cli:v3.11.0 Trying to pull repository docker.io/openshift/origin-cli ... toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[anjannath]

Red Hat Container Development kit doesn't have this issue as the images are not fetched from docker.io and instead fetched from registry.access.redhat.com

[anjannath]

Workaround is to use minishift start --docker-opt "add-registry=quay.io"

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Rose94t]

hello "Error reading $HOME/.docker/config.json: open /home/docker/.docker/config.json: no such file or directory, imagestream import credentials will not be setup" I encountered this type of error. minishift start --docker-opt "add-registry=quay.io minishift start I ran both commands and got the same error can you help me