By default, each macvlan can communicate with each other, but cannot communicate with the host! ! The reason for this is that intercommunication is prohibited for security. For example, the host machine pings the ip of the container. Although they belong to the same network segment, they cannot be pinged, and vice versa.

This article teaches you how to write a custom SELinux strategy for Docker containers

The main solution is how to configure `docker` security in the environment where `selinux` is turned on, as well as common error solutions. It is not blindly `chmod -R 777`,`--privileged=true`,`setenforce 0` , But focus on using the `selinux` security strategy

The main advantage of docker is that it can be easily deployed to the cloud, because the container has the additional benefit of running anywhere without facing dependency conflicts