How to prepare the overlay Network Experimental Environment

This article is about how to prepare the overlay network experimental environment, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

To support container communication across hosts, Docker provides overlay driver that allows users to create VxLAN-based overlay networks. VxLAN can encapsulate layer 2 data into UDP for transmission. VxLAN provides the same Ethernet layer 2 services as VLAN, but has stronger scalability and flexibility.

Docerk overlay network needs a key-value database to store network state information, including Network, Endpoint, IP and so on. Consul, Etcd, and ZooKeeper are all key-vlaue software supported by Docker, and we use Consul here.

Description of experimental environment

We will directly use the experimental environment created by docker-machine in the previous chapter. Practice various cross-host network scenarios on docker hosts host1 (192.168.56.104) and host2 (192.168.56.105), deploying supported components, such as Consul, on 192.168.56.101.

The easiest way is to run Consul as a container:

Docker run-d-p 8500 docker run-h consul-- name consul progrium/consul-server-bootstrap

After the container starts, you can access Consul through http://192.168.56.101:8500.

Next, modify the configuration file / etc/systemd/system/docker.service for host1 and host2's docker daemon.

-- cluster-store specifies the address of the consul.

-- cluster-advertise tells consul his connection address.

Restart docker daemon.

Systemctl daemon-reload

Systemctl restart docker.service

Host1 and host2 are automatically registered in the Consul database.

The above is how to prepare the overlay network experimental environment, the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.