I was looking for deep dive into container networking, this is extremely well organised and explained. Thanks Matt and Hank for creating such wonderful content.
i like the way of breaking things down, u should really post more videos like these get into the intricacies of how netwoking works, keep up the good work and thanks
Ahhh I see so we’re not abstracting and assuming responsibilities not just for networking but also for container and switch/vnic networks... awesome!!! It’s about time!!!
Does anybody know how to use the normal docker command to either... setup a reverse tunnel (ie: inside the container, 127.0.0.1:27017 binds to a port in the host so that the container can get --network=none and just be given tunnels to what it needs. or: without using Kubernetes, bind two containers into the same localhost. I need this because I can't use DNS to connect between machines. I want to disable connections to anything but 127.0.0.1 ports created by a sidecar, and have the sidecar transparently do TLS between the sidecars. I would like to not use Kubernetes. I can make a much much simpler system if I can just use straight Docker commands. Right now, the only solution seems to be to Dockerfile re-package containers to have the sidecar running along side the container.
I was looking for deep dive into container networking, this is extremely well organised and explained. Thanks Matt and Hank for creating such wonderful content.
Wow .. Pure Gold .. better than any paid courses
i like the way of breaking things down, u should really post more videos like these get into the intricacies of how netwoking works, keep up the good work and thanks
Crisp and concise ! Couldn't be better . Nice job Matt !
fantastic session guys! great how you built the container networking manually! thx Matt!
Very nice explanation covering lots of inner networking in depth. Thanks a lot
Thank you! This is the first good talk I found in 40min
Ahhh I see so we’re not abstracting and assuming responsibilities not just for networking but also for container and switch/vnic networks... awesome!!! It’s about time!!!
Extremely clear explanation - great work.
Quality stuff , thanks very much!!
Amazing video!
Love the addition of the Cisco hold music lmao
I wonder do I need to have a bridge necessarily, can I connect couple of network namespaces vi mulitple veth interfaces?
Not working for me when I test through telnet, I get "no route to host" if I use host IP but if I use 127.0.0.1, successfully connect
Does anybody know how to use the normal docker command to either... setup a reverse tunnel (ie: inside the container, 127.0.0.1:27017 binds to a port in the host so that the container can get --network=none and just be given tunnels to what it needs. or: without using Kubernetes, bind two containers into the same localhost. I need this because I can't use DNS to connect between machines. I want to disable connections to anything but 127.0.0.1 ports created by a sidecar, and have the sidecar transparently do TLS between the sidecars. I would like to not use Kubernetes. I can make a much much simpler system if I can just use straight Docker commands. Right now, the only solution seems to be to Dockerfile re-package containers to have the sidecar running along side the container.
NetOps Automation or NetDevOps Analyst/Engineer/Architect/Fox - Generalized for new Networkers including Cloud...
I can not find github repo. does any one has it?
Did you watch till the end ? he did post all the links - Webinar Resources @58:31
`sudo plotnetcfg | dot -Tpdf > topology.pdf` to generate the pdf of the current net topology on the host.
I wonder if he is aware of his watch and did it on purpose.
Why are we using docker instances? Instead of Cisco virtual devices... ;/ ugh... I understand you want to share the toys but this is a Cisco Cert...