Answers: <p>Solved it:</p>
  <blockquote>
  <p>docker network ls</p>
  </blockquote>
  <p>47ebbf46f26d   bridge    bridge    local</p>
  <blockquote>
  <p>docker network inspect bridge</p>
  </blockquote>
  <p>the bridge ip was still 172.17.0.0/16</p>
  <p>So alter the bridge ip in daemon.json</p>
  <blockquote>
  <p>cat /etc/docker/daemon.json</p>
  </blockquote>
  <pre><code>{
      &quot;bip&quot;: &quot;10.200.200.90/24&quot;,
  }
  </code></pre>
  <p>restart docker daemon and bridge is working and we can push to the registry</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-07-19T09:18:11.067Z
Answers: 2021-07-19T09:18:11.067Z
Answers: Serve Laurijssen
Body: <p>After installing docker (ubuntu) the default 172 ip was replaced with 10.200.x.x</p>
  <pre><code>sudo ip addr add dev docker0 10.200.200.90/24
  sudo ip addr del dev docker0 172.17.0.1/16
  </code></pre>
  <p>The machine's ip is 10.203.32.90</p>
  <p>Then running a private container registry with the basic command:</p>
  <pre><code>docker run -d -p 5000:5000 --restart=always --name registry registry:2
  </code></pre>
  <p>But then push to the registry fails with &quot;no route to host&quot;</p>
  <pre><code>docker push 10.203.32.90:5000/myimage
  </code></pre>
  <p>What have I done wrong or forgotten?</p>
  
Tags: <docker>
Title: no route to host container registry
UserDisplayName: Serve Laurijssen
ThreadText: # no route to host container registry
  
  (Asked by: username_0 on 2021-07-06)
  
  After installing docker (ubuntu) the default 172 ip was replaced with 10.200.x.x
  
  ```
  sudo ip addr add dev docker0 10.200.200.90/24
  sudo ip addr del dev docker0 172.17.0.1/16
  
  ```
  
  The machine's ip is 10.203.32.90
  
  Then running a private container registry with the basic command:
  
  ```
  docker run -d -p 5000:5000 --restart=always --name registry registry:2
  
  ```
  
  But then push to the registry fails with "no route to host"
  
  ```
  docker push 10.203.32.90:5000/myimage
  
  ```
  
  What have I done wrong or forgotten?
  
  **Tags:** docker
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-07-19. Score: 1 | Accepted answer
  
  Solved it:
  
  > docker network ls
  
  47ebbf46f26d bridge bridge local
  
  > docker network inspect bridge
  
  the bridge ip was still 172.17.0.0/16
  
  So alter the bridge ip in daemon.json
  
  > cat /etc/docker/daemon.json
  
  ```
  {
      "bip": "10.200.200.90/24",
  }
  
  ```
  
  restart docker daemon and bridge is working and we can push to the registry
  
  
  ---
  
  