The local area network where the host computer is located cannot be connected inside the docker container.

  question
  1. Use centos image to create a container and deploy php projects in the container. Since an interface service is to be requested from another server in t he local area network where the host is located, the http request initiated cannot be connected all the time, but it can be connected to the Internet.

2.
Host IP:172.20.20.152,
Target server IP of request interface: 172.17.3.97

Commands for Creating Docker Containers:
docker run -p 80:80 –name=mycns -it eeb3a076a0be /bin/bash

After entering the container, execute the command:
ping 172.17.3.97
The result returned 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

Installation of docker Version Information:
docker version
Return:
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 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 computer could normally connect the 172.17.3.97 machine, but after the docker service was started, it could not normally connect.

To a great god help see ha ha

You can use host-only network instead of bridging network, which is exactly the same as the host. docker run adds parameters:--net host