I appreciate that because I can understand every single word what is not so common watching many of many tutorials. I'm not English native speaker so it is very important for me to catch the meaning exactly in point.
question- multi-container control in multiple hosts or single host, means single command all container start/stop/boot/upgrade/downgrade everything. just like pod. how you can do here.
How can a service in swarm access the host network? I need the service container to access an external database hosted in a VM in the same network as the host.
Is the overlay network needed to let replicas communicate? I don't get that point. Is it used to let two different containers talk to each other (let's say a Flask API on one container on node 1 and a MongoDB database on a container on node2?) or just to let the replicas in a swarm talk to each other?
So I have a question, could this applied a swarm in general? For example, I wanted to host an nginx server on the host, run home automation software on the second node and have the requests to the nginx server for the home automation software route from node 1 to 2 via an overlay network. Wold this work or is there a simpler way to do it?
I have done the exact architecture with tis tutorial. I am verifying that hosts can ping each other, containers can ping each other and containers can ping the each hosts. But Hosts can not ping containers. What is the reason for that? I need to make an another configuration for that purpose?
Misses two important things: Security and performance. Is the overlay network encrypted by default? What's a real life performance one can get using overlay networks.
I have followed your instructions, but I am not able to ping node1 to node2, or node2 to node1. I am using EC2 instances, and I have created an INBOUND traffic allowing ICMP traffic. I don't know what else I need to check for to get this working?
I have faced the same issue. After your overlay network creation, please open up these ports in your AWS Security Group of the EC2 instances (Inbound rules). TCP and UDP port 7946 for communication among nodes UDP port 4789 for overlay network traffic After that create containers on both Nodes and you can ping each other.
In my opinion, it's one of the best tutorial ever made! It's a very complex task resumed in a simple way! PERFECT!
I appreciate that because I can understand every single word what is not so common watching many of many tutorials. I'm not English native speaker so it is very important for me to catch the meaning exactly in point.
Thank you explained very well in short duration.
question- multi-container control in multiple hosts or single host, means single command all container start/stop/boot/upgrade/downgrade everything. just like pod. how you can do here.
How can a service in swarm access the host network? I need the service container to access an external database hosted in a VM in the same network as the host.
Beautiful (lets get this up in non-prod asap) example...well done.
Is the overlay network needed to let replicas communicate? I don't get that point. Is it used to let two different containers talk to each other (let's say a Flask API on one container on node 1 and a MongoDB database on a container on node2?) or just to let the replicas in a swarm talk to each other?
Perfect Explanation mate . cheers
Hi. If I init swarm, and the second node cannot join to manager node, how can I make them connect? The two docker host can ping each eth0.
Thank you for your excellent explanation.
Thank you so much! Such a simple and clear explanation 👌🏽🙏🏽
So I have a question, could this applied a swarm in general? For example, I wanted to host an nginx server on the host, run home automation software on the second node and have the requests to the nginx server for the home automation software route from node 1 to 2 via an overlay network. Wold this work or is there a simpler way to do it?
I have done the exact architecture with tis tutorial. I am verifying that hosts can ping each other, containers can ping each other and containers can ping the each hosts. But Hosts can not ping containers. What is the reason for that? I need to make an another configuration for that purpose?
Exactly what I was recently looking to do! Thanks guys!
Brilliant video. Thanks a lot.
Misses two important things: Security and performance. Is the overlay network encrypted by default? What's a real life performance one can get using overlay networks.
Overlay networks is secured by default. Uses gossip protocol
@@shaunakkakade1325 can you comment on the speed? If you have 10gbps over fiber, whats the overhead?
Can we access a host interface from with container on an overlay network?
Thanks you, But If both hosts are in the same network how you do that??
I have followed your instructions, but I am not able to ping node1 to node2, or node2 to node1. I am using EC2 instances, and I have created an INBOUND traffic allowing ICMP traffic. I don't know what else I need to check for to get this working?
did you figure this out? I have the same issue
I have faced the same issue. After your overlay network creation, please open up these ports in your AWS Security Group of the EC2 instances (Inbound rules).
TCP and UDP port 7946 for communication among nodes
UDP port 4789 for overlay network traffic
After that create containers on both Nodes and you can ping each other.
@@princephilip2359 Thank you for your help
Excellent
I followed the video but ping is not working. I tried both sides.
perfect!! nice concise video
多主机之间的容器互通。其实，container 之间应该也走三层。就不需要overlay fabric 了。
мая твая не панимать
good lad
how easy when it works, how insane to debug when it doesn't
forest gump