The docker container cannot connect to the Lan of the host.

Use a centos image to create a container and deploy a php project in the container. to request the interface service from another server on the Lan of the host, the http request cannot be connected, but it can connect to the Internet. 2. host IP address: 172.20.0000152. target server IP address of the request interface: 1...

1. Use a centos image to create a container and deploy a php project in the container. to request the interface service from another server on the Lan of the host, the http request cannot be connected, but it can connect to the Internet.

2.
Host IP address: 172.20.0000152,
Target server IP address of the request interface: 172.17.3.97

Command for creating a Docker container:
Docker run-p 80: 80 -- name = mycns-it eeb3a076a0be/bin/bash

After entering the container, run the following command:
Ping 172.17.3.97
The returned result is:
From 172.17.0.3 icmp_seq = 1 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 2 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 3 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 4 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 5 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 6 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 8 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 9 Destination Host Unreachable

Install docker version:
Docker version
Return value:
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d/1.7.1
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d/1.7.1
OS/Arch (server): linux/amd64

3.
The host machine executes the ifconfig command and returns:
Docker0 Link encap: Ethernet HWaddr EE: 25: C5: DA: 10: 47

      inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0      inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:64400 errors:0 dropped:0 overruns:0 frame:0      TX packets:69800 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:3945235 (3.7 MiB)  TX bytes:105962604 (101.0 MiB)

Eth0 Link encap: Ethernet HWaddr F2: 3D: F0: 2B: 43: 31

      inet addr:172.20.20.152  Bcast:172.20.255.255  Mask:255.255.0.0      inet6 addr: fe80::f03d:f0ff:fe2b:4331/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:29702118 errors:0 dropped:0 overruns:0 frame:0      TX packets:583992 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:1000       RX bytes:2997801386 (2.7 GiB)  TX bytes:73288231 (69.8 MiB)

Lo Link encap: Local Loopback

      inet addr:127.0.0.1  Mask:255.0.0.0      inet6 addr: ::1/128 Scope:Host      UP LOOPBACK RUNNING  MTU:65536  Metric:1      RX packets:7059 errors:0 dropped:0 overruns:0 frame:0      TX packets:7059 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:4819120 (4.5 MiB)  TX bytes:4819120 (4.5 MiB)

Veth50f5616 Link encap: Ethernet HWaddr EE: 25: C5: DA: 10: 47

      inet6 addr: fe80::ec25:c5ff:feda:1047/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:17 errors:0 dropped:0 overruns:0 frame:0      TX packets:6 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:1014 (1014.0 b)  TX bytes:468 (468.0 b)

4.
The host machine can connect to the server 172.17.3.97 normally, but the connection fails after the docker service is started.

Let's take a look at it.

Reply content:

1. Use a centos image to create a container and deploy a php project in the container. to request the interface service from another server on the Lan of the host, the http request cannot be connected, but it can connect to the Internet.

2.
Host IP address: 172.20.0000152,
Target server IP address of the request interface: 172.17.3.97

Command for creating a Docker container:
Docker run-p 80: 80 -- name = mycns-it eeb3a076a0be/bin/bash

After entering the container, run the following command:
Ping 172.17.3.97
The returned result is:
From 172.17.0.3 icmp_seq = 1 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 2 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 3 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 4 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 5 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 6 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 8 Destination Host Unreachable
From 172.17.0.3 icmp_seq = 9 Destination Host Unreachable

Install docker version:
Docker version
Return value:
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d/1.7.1
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d/1.7.1
OS/Arch (server): linux/amd64

3.
The host machine executes the ifconfig command and returns:
Docker0 Link encap: Ethernet HWaddr EE: 25: C5: DA: 10: 47

      inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0      inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:64400 errors:0 dropped:0 overruns:0 frame:0      TX packets:69800 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:3945235 (3.7 MiB)  TX bytes:105962604 (101.0 MiB)

Eth0 Link encap: Ethernet HWaddr F2: 3D: F0: 2B: 43: 31

      inet addr:172.20.20.152  Bcast:172.20.255.255  Mask:255.255.0.0      inet6 addr: fe80::f03d:f0ff:fe2b:4331/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:29702118 errors:0 dropped:0 overruns:0 frame:0      TX packets:583992 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:1000       RX bytes:2997801386 (2.7 GiB)  TX bytes:73288231 (69.8 MiB)

Lo Link encap: Local Loopback

      inet addr:127.0.0.1  Mask:255.0.0.0      inet6 addr: ::1/128 Scope:Host      UP LOOPBACK RUNNING  MTU:65536  Metric:1      RX packets:7059 errors:0 dropped:0 overruns:0 frame:0      TX packets:7059 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:4819120 (4.5 MiB)  TX bytes:4819120 (4.5 MiB)

Veth50f5616 Link encap: Ethernet HWaddr EE: 25: C5: DA: 10: 47

      inet6 addr: fe80::ec25:c5ff:feda:1047/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:17 errors:0 dropped:0 overruns:0 frame:0      TX packets:6 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0       RX bytes:1014 (1014.0 b)  TX bytes:468 (468.0 b)

4.
The host machine can connect to the server 172.17.3.97 normally, but the connection fails after the docker service is started.

Let's take a look at it.

Found Cause: http://dev.bidlust.com /? P = 103

You can not use a bridge network. you can use only the host network, which is exactly the same as the host. add the following parameters for docker run:--net host

It should have been blocked by the firewall.