Create a container without network configuration
[root@localhost ~]# docker run -i -t --rm --net=none alpine sh / #
Open another terminal
View container id
[root@localhost ~]# docker ps -a
Find process id
[root@localhost ~]# docker inspect -f '{{.State.Pid}}' 2aefc41dbdeb 9076 [root@localhost ~]# pid=9076
Create namespace
[root@localhost ~]# mkdir -p /var/run/netns [root@localhost ~]# ln -s /proc/$pid/ns/net /var/run/netns/$pid
View the IP and subnet mask information of the bridge network card
[root@localhost ~]# ip addr show docker0 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN link/ether 02:42:8e:e7:64:4a brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global docker0 valid_lft forever preferred_lft forever
Create A pair of "veth pair" interfaces A and B
[root@localhost ~]# sudo ip link add A type veth peer name B
Bind interface A to bridge docker0
[root@localhost ~]# sudo brctl addif docker0 A
And enable it
[root@localhost ~]# sudo ip link set A up
Put the B interface into the container's network namespace
[root@localhost ~]# sudo ip link set B netns $pid
Named eth0
[root@localhost ~]# sudo ip netns exec $pid ip link set dev B name eth0
Open network interface B
[root@localhost ~]# sudo ip netns exec $pid ip link set eth0 up
Configure an available IP (bridge segment)
[root@localhost ~]# sudo ip netns exec $pid ip addr add 172.18.0.99/16 dev eth0
Configure default gateway
[root@localhost ~]# sudo ip netns exec $pid ip route add default via 172.18.0.1
Finally, go back to the container and check the network card configuration
/ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 18: eth0@if19: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 6e:b9:75:8e:f4:99 brd ff:ff:ff:ff:ff:ff inet 172.18.0.99/16 scope global eth0 valid_lft forever preferred_lft forever / # ping baidu.com PING baidu.com (123.125.114.144): 56 data bytes 64 bytes from 123.125.114.144: seq=0 ttl=53 time=2.827 ms 64 bytes from 123.125.114.144: seq=1 ttl=53 time=2.900 ms ^C --- baidu.com ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 2.827/2.863/2.900 ms