Insecure registry required for installer - 172.30.0.0/16

[kpiwko]

Oc cluster up failed with a docker prerequisite

TASK [oc-cluster-up : Cluster up] **********************************************
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "oc cluster up --service-catalog=true --host-config-dir=/Users/kpiwko/devel/mobile/mcp-standalone/ui --host-data-dir=/Users/kpiwko/devel/mobile/mcp-standalone/ui/openshift-data --host-pv-dir=/Users/kpiwko/devel/mobile/mcp-standalone/ui/openshift-pvs --host-volumes-dir=/Users/kpiwko/devel/mobile/mcp-standalone/ui/openshift-volumes --routing-suffix=192.168.37.1.nip.io --public-hostname=192.168.37.1 --version=v3.7.0-rc.0 --image=openshift/origin", "delta": "0:00:00.214286", "end": "2017-11-13 15:57:26.278591", "failed": true, "rc": 1, "start": "2017-11-13 15:57:26.064305", "stderr": "", "stderr_lines": [], "stdout": "Starting OpenShift using openshift/origin:v3.7.0-rc.0 ...\n-- Checking OpenShift client ... OK\n-- Checking Docker client ... OK\n-- Checking Docker version ... OK\n-- Checking for existing OpenShift container ... OK\n-- Checking for openshift/origin:v3.7.0-rc.0 image ... OK\n-- Checking Docker daemon configuration ... FAIL\n   Error: did not detect an --insecure-registry argument on the Docker daemon\n   Solution:\n\n     Ensure that the Docker daemon is running with the following argument:\n     \t--insecure-registry 172.30.0.0/16\n\n     You can run this command with --create-machine to create a machine with the\n     right argument.", "stdout_lines": ["Starting OpenShift using openshift/origin:v3.7.0-rc.0 ...", "-- Checking OpenShift client ... OK", "-- Checking Docker client ... OK", "-- Checking Docker version ... OK", "-- Checking for existing OpenShift container ... OK", "-- Checking for openshift/origin:v3.7.0-rc.0 image ... OK", "-- 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:", "     \t--insecure-registry 172.30.0.0/16", "", "     You can run this command with --create-machine to create a machine with the", "     right argument."]}
    to retry, use: --limit @/Users/kpiwko/devel/mobile/mcp-standalone/installer/playbook.retry

Adding insecure registry fixed the problem

[maleck13]

@kpiwko thanks for this, I will update the docs when i get a minute

[david-martin]

This is already covered in the Requirements section here https://github.com/feedhenry/mcp-standalone/blob/master/docs/walkthroughs/local-setup.adoc#firewall-requirements-required Where we say to do Steps 2 & 3 from the oc cluster guide at https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#linux

The 'oc cluster' pre-req check seems to be picking up on the problem, so I don't think we should add additional automated pre-req checking to our install script.

@maleck13 @kpiwko I'd say we can close this, unless there's something I've missed

[kpiwko]

Thanks @david-martin. I've skipped this section as it talks about firewall rules in the headline, not Docker Registry. Not sure how to better word it though - the issue is not on documentation side ;-). Closing.