Thanks Elton! This was fantastic quick walkthrough. I would suggest making more videos around different aspects of docker, and publishing them. Would be very useful to the community. I have seen your many other courses, and must say your explanation style is superb.
I found this video EXTREMELY helpful. Completely making swarm approachable. I'd love to see it updated with the current docker version. But thanks for doing this Elton.
This is a very clear and concise walk-through of an introduction to docker swarms. It is especially effective with the combination of diagrams and command line. Well done!
This is extraordinary! I am experimenting now to use Docker swarm to distribute 5G mobile networking SDN nodes, and simulate DoS attack on mobile infrastructure with prevention mechanisms for my master (and later PhD thesis). The redundancy thing (if a node fails, other prevails) is a godly thing! This can be the Chuck Norris of mobile network security. Great video :) Cheers!
nice video Elton ---- u have great talent and I would request you to make more videos on all the knowledge you have ---which is help full for others like me ______thanks elton
Dude this has been so helpful thank you!!! I have been messing up trying to create docker machine swarm nodes and trying to use swarm that way but the information that the engine and the docker swarm commands are different has had me running in circles!! Although i dont see a node column when im running the docker task ls command.
Thanks a lot Elton for this walk-through showcasing the cool Swarm features (now) integrated in Docker Engine v1.12 If anyone else wishes to test drive this on local Vagrant/Virtual box setup , they can refer to a sample vagrant file from here : github.com/thomgit/docker-swarm
Thanks Elton! for the simple yet amazing explanation.I have a question regarding manager node, what if the manager node goes down is there any way it can delegate the responsibility to some other node.
Very good tutorial, thank you. However, the load-balancing needs further explanation as it lacks a final example of connection from the browser when replicas are spun up. Can you get rid of the initial external balancer and simply connect to the first one node expecting the swarm to re-route the request to the nodes where the tasks are running?
May I suggest you to have multiple tabs open in the terminal, so we dont have to keep ssh-ing multiple times. It was a perfect introduction otherwise. Thank you.
Thank You Elton this is a nice simple and clear tutorial as introduction to docker swarm ! i have a question what if an node with container created already with docker run command ,can swarm recognize those containers ,can i replicate theme to the others node ? thanks in advance
thanks. can you also show how to add --constraint to docker service? i've tried adding --label name=node1 to the daemon and --constraint node.labels.name==node1 or --constraint node==node1, with no luck.
I see the benefits of the swarm for business use. For home use, maybe not so much. Could I run a tvheadend docker in the swarm? It can only handle a certain number of streams on the pi before the cpu maxes out. It would be great if I could install it in a swarm and if one server has the maximum number of streams it would spawn another instance of tvheadend on another node
Thank you for this great presentation! I have two questions please: how can i connect different hosts machines into the same network ? and how can i say that this particular machine is connected to this overlay network (if overlay network is the solution) ?
Thx a lot for your sharing, Captain! I'm new in swarm and I'm using AWS EC2 as nodes for swarm. I created 3 nodes including swarm manager and I cannot join swarm like you did in the video. each node has its inner IP and a public IP different from it. as your nodes are all in the same subnet, what can I do to join swarm? should I need token to join and which IP should I use?
Thank you Elton! That was really cool! :-) Can you tell what happens if node-00 (the manager node) fails? Does docker swarm reassign another node as the new manager or would the whole swarm go down?
Hi Andy, glad you liked it. In this case there's only one manager, so if you lose it then you can't manage the swarm until it comes back. In production you'd have 3 or 5 managers, one is the active leader, and the others elect a new leader if it goes down.
In your video, you shutdown swarm-03 to simulate a failure. What happens when swarm-03 boots again and joins the cluster? Would the tasks be restored to swarm-03, or would they continue to run on the other swarm nodes?
Nice video. What happen if an unknown client in the subnet launches the join command? It will ba added automatically to the cluster? Is there a possibility to confirm the adding from the manager?
How do you use docker join without token? I try but without sucess. "Error response from daemon: rpc error: code = 3 desc = A valid join token is necessary to join this cluster".
In the new version of Docker, the tokens are must. So when you will run the "docker service init" you will get the join command in result, which you can hit in your other nodes.
