title: Docker 1.10 container's IP in LAN
body: <p>Since Docker 1.10 (and libnetwork update) we can manually give an IP to a container inside a user-defined network, and that's cool!</p>
  
  <p>I want to give a container an IP address in my LAN (like we can do with Virtual Machines in "bridge" mode). My LAN is 192.168.1.0/24, all my computers have IP addresses inside it. And I want my containers having IPs in this range, in order to reach them from anywhere in my LAN (without NAT/PAT/etc...).</p>
  
  <p>I obviously read Jessie Frazelle's <a href="https://blog.jessfraz.com/post/ips-for-all-the-things/">blog post</a> and a lot of others post here and everywhere like :</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/22641828/how-to-set-a-docker-containers-ip">How to set a docker container&#39;s iP?</a></li>
  <li><a href="https://stackoverflow.com/questions/35218621/how-to-assign-specific-ip-to-container-and-make-that-accessible-outside-of-vm-ho">How to assign specific IP to container and make that accessible outside of VM host?</a></li>
  </ul>
  
  <p>and so much more, but nothing came out; my containers still have IP addresses "inside" my docker host, and are not reachable for others computers on my LAN.</p>
  
  <p>Reading Jessie Frazelle's blog post, I thought (since she uses public IP) we can do what I want to do?</p>
  
  <p><strong>Edit</strong>: Indeed, if I do something like :</p>
  
  <pre><code>network create --subnet 192.168.1.0/24 --gateway 192.168.1.1 homenet
  docker run --rm -it --net homenet --ip 192.168.1.100 nginx
  </code></pre>
  
  <p>The new interface on the docker host (br-[a-z0-9]+) take the '--gateway' IP, which is my router IP. And the same IP on two computers on the network... BOOM</p>
  
  <p>Thanks in advance.</p>