Answers: <p>This error happens because the <code>oc cluster up</code> command spawns a Docker registry. The <code>172.30.0.0/16</code> IP range is probably corresponding to your Docker bridge network. As the registry will run in a container with an unpredictable IP address, you must indicate the IP range (<code>--insecure-registry 172.30.0.0/16</code>).</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-12-03T14:59:55.793Z
Answers: 2019-12-03T14:59:55.793Z
Answers: Hedi Nasr
Body: <p>According to <a href="https://blog.hostonnet.com/did-not-detect-insecure-registry-argument-docker-daemon" rel="nofollow noreferrer">this blog</a> one has to change the docker daemon:</p>
  
  <blockquote>
  <pre><code>/usr/bin/dockerd --insecure-registry 172.30.0.0/16 -H fd://
  </code></pre>
  </blockquote>
  
  <p>but I wonder why the error occurs and how to fix it properly?</p>
  
Tags: <openshift>
Title: What is the proper way to fix `error: did not detect an --insecure-registry argument on the Docker daemon` while running `oc cluster up`?
UserDisplayName: 030
ThreadText: # What is the proper way to fix `error: did not detect an --insecure-registry argument on the Docker daemon` while running `oc cluster up`?
  
  (Asked by: username_0 on 2019-12-03)
  
  According to [this blog](https://blog.hostonnet.com/did-not-detect-insecure-registry-argument-docker-daemon) one has to change the docker daemon:
  
  > ```
  > /usr/bin/dockerd --insecure-registry 172.30.0.0/16 -H fd://
  >
  > ```
  
  but I wonder why the error occurs and how to fix it properly?
  
  **Tags:** openshift
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-12-03. Score: 2 | Accepted answer
  
  This error happens because the `oc cluster up` command spawns a Docker registry. The `172.30.0.0/16` IP range is probably corresponding to your Docker bridge network. As the registry will run in a container with an unpredictable IP address, you must indicate the IP range (`--insecure-registry 172.30.0.0/16`).
  
  
  ---
  
  