![]() ![]() Now we are going to create a bridge in this namespace, give it an IP address and bring the interface up: docker0:~$ sudo ip netns exec overns ip link add dev br0 type bridgeĭocker0:~$ sudo ip netns exec overns ip addr add dev br0 192.168.0.1/24ĭocker0:~$ sudo ip netns exec overns ip link set br0 up The first thing we are going to do now is to create an network namespace called “overns”: sudo ip netns add overns If you have tried the commands from the first two posts, you need to clean-up your Docker hosts by removing all our containers and the overlay network: docker0:~$ docker rm -f $(docker ps -aq) ![]() In this third post, we will see how we can create our own overlay with standard Linux commands. In part 2 we have looked in details at how Docker uses VXLAN to tunnel traffic between the hosts in the overlay. In part 1 of this blog post we have seen how Docker creates a dedicated namespace for the overlay and connect the containers to this namespace. ![]() Temps de lecture : 18 minutes Introduction ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |