title: Starting OpenShift cluster never ends when starting minishift or takes to much memory
body: <p>Whenever I run the command to start Minishift with the virtualbox driver to the OS host it takes a crazy time and it never ends. Sometimes I even get an error message on storage limit being reached.</p>
  
  <p>I wonder if it is an error of Persistent storage volume configuration and usage that is described <a href="https://docs.openshift.org/latest/minishift/troubleshooting/troubleshooting-getting-started.html#persistent-storage-check" rel="noreferrer">here</a></p>
  
  <pre><code>mike@mike-thinks:~$ minishift start --vm-driver=virtualbox
  -- Starting profile 'minishift'
  -- Check if depereccated options are used ... OK
  -- Checking if https://github.com is reachable ... OK
  -- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
  -- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
  -- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
  -- Checking if VirtualBox is installed ... OK
  -- Checking the ISO URL ... OK
  -- Checking if provided oc flags are supported ... OK
  -- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
  -- 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 ... 8% used OK
  -- OpenShift cluster will be configured with ...
     Version: v3.9.0
  -- Copying oc binary from the OpenShift container image to VM .... OK
  -- Starting OpenShift cluster ..............................................
  </code></pre>
  
  <p>What I can do ? I'm following <a href="https://docs.openshift.org/latest/minishift/getting-start" rel="noreferrer">this tutorial</a> and I just want to get to the stage that allows me to add <code>oc</code> to the PATH</p>
  
  <h3>Update: new error during openshift cluster start</h3>
  
  <pre><code>-- Starting OpenShift cluster ...........Error during 'cluster up' execution: Error starting the cluster. ssh command error:
  command : /var/lib/minishift/bin/oc cluster up --use-existing-config --host-volumes-dir /var/lib/minishift/openshift.local.volumes --host-pv-dir /var/lib/minishift/openshift.local.pv --host-config-dir /var/lib/minishift/openshift.local.config --host-data-dir /var/lib/minishift/hostdata --public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io
  err     : exit status 1
  output  : Deleted existing OpenShift container
  Using nsenter mounter for OpenShift volumes
  Using public hostname IP 192.168.99.100 as the host IP
  Using 192.168.99.100 as the server IP
  Starting OpenShift using openshift/origin:v3.9.0 ...
  -- Starting OpenShift container ... 
     Starting OpenShift using container 'origin'
     Waiting for API server to start listening
  FAIL
     Error: cannot access master readiness URL https://192.168.99.100:8443/healthz/ready
     Details:
       Last 10 lines of "origin" container log:
       E0625 14:47:40.905680    2341 proxier.go:252] Error removing userspace rule: error checking rule: fork/exec /usr/sbin/iptables: exec format error: 
       E0625 14:47:40.908353    2341 proxier.go:259] Error removing userspace rule: error checking rule: fork/exec /usr/sbin/iptables: exec format error: 
       E0625 14:47:40.910681    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-PORTALS-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 
       E0625 14:47:40.913452    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-PORTALS-HOST": fork/exec /usr/sbin/iptables: exec format error: 
       E0625 14:47:40.919209    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-HOST": fork/exec /usr/sbin/iptables: exec format error: 
       W0625 14:47:40.931698    2341 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
       E0625 14:47:40.932412    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 
       E0625 14:47:40.938345    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-NON-LOCAL": fork/exec /usr/sbin/iptables: exec format error: 
       W0625 14:47:40.941639    2341 iptables.go:151] Error checking iptables version, assuming version at least 1.4.11: fork/exec /usr/sbin/iptables: exec format error
       F0625 14:47:40.949329    2341 network.go:177] error: Could not initialize Kubernetes Proxy. You must run this process as root (and if containerized, in the host network namespace as privileged) to use the service proxy: failed to initialize iptables: error creating chain "KUBE-PORTALS-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 
  
  
     Caused By:
       Error: Get https://192.168.99.100:8443/healthz/ready: dial tcp 192.168.99.100:8443: getsockopt: connection refused
  </code></pre>