minishift: Unable to use private insecure registry during start

We have option to specify insecure registry as part of minishift start command through --insecure-registry. However, I am unable to use it.

Am I doing wrong or may be missing something here ?

Steps to reproduce

• Setup private registry (192.168.1.101 is my host ip)

docker run -d -p 192.168.1.101:5000:5000 --restart=always --name registry2 -v /home/budhram/_work/docker-registry:/var/lib/registry registry:2

• Use above registry during minishift start

$ minishift start --insecure-registry 192.168.1.100/10

I am getting following error:

$ minishift start --insecure-registry 192.168.1.100/10
Starting local OpenShift cluster using 'kvm' hypervisor...
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.5.0 image ... 
   Pulling image openshift/origin:v1.5.0
   Pulled 0/3 layers, 3% complete
   Pulled 0/3 layers, 15% complete
   Pulled 0/3 layers, 37% complete
   Pulled 1/3 layers, 39% complete
   Pulled 1/3 layers, 46% complete
   Pulled 1/3 layers, 53% complete
   Pulled 1/3 layers, 60% complete
   Pulled 1/3 layers, 67% complete
   Pulled 1/3 layers, 74% complete
   Pulled 1/3 layers, 81% complete
   Pulled 2/3 layers, 86% complete
   Pulled 2/3 layers, 89% complete
   Pulled 2/3 layers, 92% complete
   Pulled 2/3 layers, 95% complete
   Pulled 2/3 layers, 98% complete
   Pulled 3/3 layers, 100% complete
   Extracting
   Image pull complete
-- Checking Docker daemon configuration ... FAIL
   Error: did not detect an --insecure-registry argument on the Docker daemon
   Solution:

     Ensure that the Docker daemon is running with the following argument:
     	--insecure-registry 172.30.0.0/16

Error starting the cluster.

Anyone able to use it successfully?