![]() It is not possible to have a single host adapter (i.e eth0) have two macvlans running at the same time. private overlay network to allow all 3 nodes to talk to each other for purpose of sync.public macvlan network used in the adgaurd2 container.public macvlan config for adguard2 and is dsitributed to all 3 docker nodes.public macvlan network used in the adgaurd1 container.public macvlan config for adguard1 and is dsitributed to all 3 docker nodes.We have the following networks in this config: ![]() Also macvlan in swarm is a quite complex and a little werid. Wow, this is the most complex network setup because i need each adguard instance to be able to have its own MAC and IP address and i needed the adguard sync container to be able to sync between the two nodes. I chose to use the glusterfs volume driver to make these so they are available on any node. I also wanted to use native ports like 443 but have other services that need to use that too so rather than use host networking i used macvlan/ This is not rquired but i wanted to make this one interesing :-) State Considerations for SWARMĮach of the two nodes needs to have their own confgi and worker mounts. ![]() I also wanted adguard to accurately record the client host names accessing adgaurd - this meant i needed to use macvlan networking. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |