IP 192.168.0.1 used by host?

[gonzalo]

I can run container fine and install & run chrome normally. But when I try to navigate to our LAN server (located in 192.168.0.1) connection is rejected. A NMAP scan from inside the the container shows dns is correctly result but that ip redirects to local instead of remote machine:

# nmap 192.168.0.1        

Starting Nmap 7.40 ( https://nmap.org ) at 2018-08-27 09:19 UTC
Nmap scan report for xxxxxxxxxx.xxxxxxxxx.local (192.168.0.1)
Host is up (0.000036s latency).
Not shown: 997 closed ports
PORT     STATE SERVICE
111/tcp  open  rpcbind
5800/tcp open  vnc-http
5900/tcp open  vnc

Which service is taking the 192.168.0.1 ip? Ifconfig doesn't show any device

# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.2  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:ac:11:00:02  txqueuelen 0  (Ethernet)
        RX packets 54140  bytes 42405776 (40.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 46411  bytes 13510655 (12.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1  (Local Loopback)
        RX packets 71085  bytes 13893319 (13.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 71085  bytes 13893319 (13.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[jlesage]

Is 192.168.0.1 the host running the container?

[gonzalo]

Sorry for leaving this post here. The problem is related to my docker installation that is doing some weird stuff with my vpn, lan & other. Running container in our servers network worked fine. Thanks for your help and this useful image