Docker networking is CRAZY!! (you NEED to learn it)
ฝัง
- เผยแพร่เมื่อ 22 พ.ค. 2024
- Don’t leave yourself unprotected, get the best protection by checking out BitDefender Premium Security at the link below.
bit.ly/BitdefenderNC
Today you are going to explore the mysterious world of Docker networking. From the default bridge to the blackhole of none. NetworkChuck is going to help you navigate this fascinating technology.
🔥🔥 Guide and Walkthrough: ntck.co/Docker-networking
Follow Christian Everywhere:
TH-cam: / thedigitallifetech
Twitter: @christian_tdl
Instagram: christian_tdl
Linkedin: Christian Lempa
🔥🔥Join the NetworkChuck Academy!: ntck.co/NCAcademy
**Sponsored by Bitdefender
SUPPORT NETWORKCHUCK
---------------------------------------------------
➡️NetworkChuck membership: ntck.co/NCAcademy
☕☕ COFFEE and MERCH: ntck.co/coffee
Check out my new channel: ntck.co/ncclips
🆘🆘NEED HELP?? Join the Discord Server: / discord
STUDY WITH ME on Twitch: bit.ly/nc_twitch
READY TO LEARN??
---------------------------------------------------
-Learn Python: bit.ly/3rzZjzz
-Get your CCNA: bit.ly/nc-ccna
FOLLOW ME EVERYWHERE
---------------------------------------------------
Instagram: / networkchuck
Twitter: / networkchuck
Facebook: / networkchuck
Join the Discord server: bit.ly/nc-discord
0:00 ⏩ Intro
1:17 ⏩ What do you need?
2:19 ⏩ Let’s do this!
3:33 ⏩ The first network: The Default Bridge
10:44 ⏩ The second network: The User-defined Bridge
15:38 ⏩ The third but best network: The MACVLAN
22:51 ⏩ MACVLAN, trunked: MACVLAN 802.1q
25:01 ⏩ The fourth network: IPVLAN (L2)
27:05 ⏩ The fifth and my favorite network: IPVLAN (L3)
36:40 ⏩ The sixth network: Overlay network
37:35 ⏩ None
38:11 ⏩ Outro
AFFILIATES & REFERRALS
---------------------------------------------------
(GEAR I USE...STUFF I RECOMMEND)
My network gear: geni.us/L6wyIUj
Amazon Affiliate Store: www.amazon.com/shop/networkchuck
Buy a Raspberry Pi: geni.us/aBeqAL
#docker #dockernetworks #Networks - วิทยาศาสตร์และเทคโนโลยี
Don’t leave yourself unprotected, get the best protection by checking out BitDefender Premium Security at the link below.
bit.ly/BitdefenderNC
Today you are going to explore the mysterious world of Docker networking. From the default bridge to the blackhole of none. NetworkChuck is going to help you navigate this fascinating technology.
🔥🔥 Guide and Walkthrough: ntck.co/Docker-networking
Follow Christian Everywhere:
TH-cam: th-cam.com/users/thedigitallifetech
Twitter: @christian_tdl
Instagram: christian_tdl
Linkedin: Christian Lempa
0:00 ⏩ Intro
1:17 ⏩ What do you need?
2:19 ⏩ Let’s do this!
3:33 ⏩ The first network: The Default Bridge
10:44 ⏩ The second network: The User-defined Bridge
15:38 ⏩ The third but best network: The MACVLAN
22:51 ⏩ MACVLAN, trunked: MACVLAN 802.1q
25:01 ⏩ The fourth network: IPVLAN (L2)
27:05 ⏩ The fifth and my favorite network: IPVLAN (L3)
36:40 ⏩ The sixth network: Overlay network
37:35 ⏩ None
38:11 ⏩ Outro
Okay
Learn language correction by David wyn Miller through mathematical interface.
th-cam.com/video/6iJQETEJNQc/w-d-xo.html
Bitdefender used to be my go-to until it started quarantining everything on my computer including itself. They addressed it in an update later but the damage was done.
You're one of my favorite teachers Chuck! I invested in networkchuck academy because I believe in you
Finally, someone who explains it at a detailed level but also doesn’t assume everyone watching is a networking expert. This was the perfect video for this subject
I so hear you!!!
Yeah, this is the one where it all made sense finally for me.
Admit now.... We all want a Teacher Like Him💯💕💕💕💯
How do you mean? We *have* him as a teacher, all you need to learn is to pay attention for 30mins. And its free.
@@sliceoflife5812 bro i meant... We need teachers like him at college.... 🙂
@@sliceoflife5812 Be cool my friend.... He may be joking🙂
Biggest issue with my Cybersecurity degree is everything is online. Like, why am I even paying for this with little to no instructor interaction. There's a huge campus for the school too. 🤷♂️
He's gives tid bits of knowledge. There is a reason he quit cbt.
Man, I'm a Brazilian and come to your channel to watch funny and instructive videos ❤❤
This should be on the official Docker page. Absolutely fantastic!!!! Loved the content. Researching this has been mind numbing, but this right here, is the jackpot. It's amazing how you dig into the actual networking while still keeping everything light and entertaining.
Yeah, this is definitely what I needed right now. Diving into docker and had just a basic understanding of docker networking from prior use on my unraid server. Digging into the weeds of running my own docker containers managed through Portainer on a new enterprise server box I recently got for my homelab. The way you present this is just awesome!
I totally agree about that... He is a funny guy with a funny way to teach. I was using LXD/LXC for containerization but just a few weeks now I'm into Docker and this network stuff makes me happy because i figured it to run on LXC this way but did not know it was possible to use macvlan for Docker as well. So LXD goes and Docker stays with Portainer its realy funny and easy to use.
I am running a few dockers and VMs on a new Unraid Server now. Would love to connect we can share ideas? This video was perfect for me too, but even still, I get so confused on what is talking with what at times. I managed to get home assistant on Unraid but it isn't working externally, while other apps like Plex is working. My head is crazy
yes yes I too am running docker containers managed through Portainer on my "enterprise server" cough .. raspberry pi with OMV ... cough
One network shortcut I like is “ip -br a” which hides a lot of the cruft and just lists the adapters and addresses.
Try ip -4 -br a
brah . . . :)
I always thought Docker was dumb when you can just spin up a virtual machine, but after watching this my mind has changed. You can create dockers WAY MORE QUICKLY than installing new ISO's to VM's!! Thanks for this!
As Chuck said, if you are using the default bridge network you can't use the docker dns with containers name as ip address, instead you can use the id of the container and it will work fine. Also you can get a container id by the environment variable named HOSTNAME that is automatically created with the container, so this way you don't need to hardcode the id.
This is perfect! I’ve been looking into learning more about docker and your videos always have the information I’m looking for.
The L3 IP vlan is amazing! Unique IP for each container is much better than trying to map ports to every container
This is probably the most comprehensive Docker Networking tutorial of any kind and it is under 40 mins. NetworkChuck you are awesome !
Dude I can’t tell you how much I appreciate your videos. I just deployed adguard as a docker container to my home network. You make it so much fun to work through. Thanks! Im learning a bunch.
So cool. As mainly a front-end dev, I'm finding out it's STILL unavoidable to learn a bit about containers, deployment and networking. I've memorized enough of the basic workflows to get me by, but your explanations actually have me UNDERSTANDING what's going on under the hood, and why! Love your lingo, your playful approach, and ESPECIALLY your drawings. Makes me feel like cracking open my laptop on a Saturday night! Thanks Chuck!
I've been doing Docker for many years and it's still great to get an all-in-one summary of docker networking which can seem like wizardry at times.
I wish I'd had this video a few years ago. It explains the subject so clearly. I've been using a messy workaround to get unique IPs for each of my containers, when Docker had the solution for me all along. Thanks for finally helping me understand it!
This video is absolutely incredible. To top it off - awesome quality, well spoken, and fun. Thank you! Subscribed!
By far the best video on "docker networks" I ever saw...and a saw a lot of them. Chuck, I just love your awesome work and knowledge sharing! Keep it going!
This is crazy. Diving in some topic in software engineering is not difficult. The hardest part is how you gonna begin with it. Your video is the best guidance for the beginners. Thank you!
This was by far the best explanation on docker networking I have ever seen. Throw away all books and watch this. Thanks a million. Great stuff
Seriously man, I haven't seen somebody so passionate explaining networking stuff. Thanks for the explanation and elaboration, it was fantastic!
He's Network Chuck ;)
Chuck, great video, thanks for keeping this entertaining, as this topic be a bit dry when researching it on the docker docs. One additional tip that I like to do with docker networking is switching the networks the containers are connected too or adding the containers to existing docker networks. Instead of stopping and deleting the containers , I just run 'docker network connect | disconnect '. You may already be aware of it, it's just something I like to use, as I hate rebuilding the containers. Thanks again
Boom ty
I never seen a teacher like you chuck .. y make the IT easy and funny good luck chuck
Thanks that was one awesome style of sharing; mad learning; love it
The way you teach with examples and diagrams for visualization into a network, it makes Docker more interesting to learn.
Really Appreciated.
Thanks for the Video !!
Man, what a video! Absolute MUST for everyone that is working and learning Docker. Thank you for providing so valuable information!
@9:35, rather than up a bunch of times use Ctrl+R, type a string match to the command you're looking for, it will lookup in your command history filtered by that string.
If the first result isn't it pressing Ctrl+r again will go to the next most recent one, etc.
Excellent video. And I love the enthusiasm and appreciation of just how incredibly cool it is to create virtual networks of all kinds.
Awesome work, the passion, the tone, the cuts (frame/camera/screen transitions) etc! Kudos. Thanks man!
Great content. Gave me enough to delve deeper into container networking. Slight differences between docker and podman (that threw me for a second - podman inspect on a container bridge doesn't show you container IP addresses), but that hasn't stopped me from learning some very useful stuff. Thanks!
I never actually use what you explain but I love learning what it is
it is awesome! thank you for straightforward explanation! cheers!
Thank you for explaining this! Great job!
Thanks you so much.
I needed this for setting up a docker container as a wireguard client to a remote network. The container is now the gateway for the other physical machines in my network too.
Man, usually I don't like to leave comments, but not today! Amazing explanation and material supply! 5 stars⭐
You are just an amazing teacher 😊
Love your presentation methods, and the detail you go into. Shall be watching more of your videos for sure. Thank you :)
I am doing this at home right now at 10pm , instead of playing a video game. I have screamed like 4 times at how cool and powerful this is. This is also solving a current project/contract I have. Can't thank you enough man!
You're one of my favorite teachers Chuck! I invested in networkchuck academy because I believe in you
Love the effort u put in to edit ur videos
Greatly appreciate this video. Very well done. Thanks Chuck!
A great overview of Docker networking modes with their pluses and minuses. Defiantly worth a view and review when you are about to play or setup some new Docker systems.
you're still using virtual box instead of WSL?
You know he's in serious mode when he's not doing it on LieNode.
Is linode no good?
@@MrMustachehead for lab environment I love it. But I wouldn't use it for critical production environments
@@bieggerm what would you use instead?
@@dynapilot definitely some hyperscaler
I love you went into the details of what's causing problem on the network switch.
Very helpful video. I want to lean more about the IPVLAN L3 but need to understand port forwarding a bit more since I only have a single public IP on my home network (FiOS router) and from there my lab network is on a totally different IP network using a pfSense router and HAProxy. One thing though… I think you forgot to include “container” as a network type. For example, I have a VPN container and then have multiple other containers running inside it. The other containers do not get their own IPs or ports. The VPN uses user-defined bridged network and the ports are mapped inside that container. This lets me choose which containers on my host run through the VPN and which do not.
Great video. Question: What tool do you use to annotate your screen? What do you use to sketch? Also any recommendations for zoom utility for Ubuntu so we can zoom into something during presentations. (Sorry if you have answered these before; if so, please point me to them).
Thanks so much for a concise yet complete video! You’re explanation is brilliant and super helpful. Thanks!!
Dude, you are awesome! It's so good to watch such rich technical content that's also fast, colorful, and funny. Your presentation and editing are very good. Keep up the excellent work!
Hey Chuck,
Awesome video! I would like to share some of my experience with you. You mentioned busybox images, from my personal security perspective I suggest never using these images in production (so it includes for example alpine linux image). The reason is simply as we all know containers are not the same type of isolation as hypervisor, all processes launched in container are visible to the host and we want to create the best security for our containers because of that - so we want the block some malicious commands inside our container like "mount" (this should definitely be blocked lol). Docker does that by default using awesome app called Apparmor and it's profiles, but the problem is busybox kind of boxes all of these normally separate executables in one big executable, meaning we cannot block specific commands, we must either block entire busybox or nothing as everything is inside one executable. THIS makes even the default apparmor profile not work and commands like MOUNT are available to container. VERY dangerous in production, so I do not personally suggest using busybox images for production.
I think he was using busybox just so he could enter the containers and run commands like ping and ip addr, don't think he said to use it in prod
Euhm mount is not available on alpine and docker block this command by default....
And don't forget that alpine is made to be used as docker image, and they can be used on most production environments
@@grmancool Hey, yes I know, it's just information comment for other people trying out docker :)
@@CyberFreaked this is incorrect mount is very much available in alpine linux images with exception of images that are non-root (of course people should use these, but some applications are just problematic in non root environment).
better idea: use buildah to create your images and only have the absolute minimum in them what you actually need instead of basing it on an OS image
Docker networking is actually surprisingly similar to (FreeBSD) jail networking, I always thought they would work completely differently.
Good job on the progress bar indicator it kept me watching throught the entire video and kept me interested.
Outstanding! exactly explained I was looking for; Thanks
This was an amazing watch as a CCNP who struggled with docker networking (Visual learner). Please make the same thing but for Kubernetes 😂 (Kube-router, flannel, metalLB, etc)
I think he already has, check his channel
One of the driving reasons using docker is to get away from VMs. You add an extra layer of overheard by running docker on a VM. You can run docker any OS, though preferred is Linux. They are also very easy to clean up, so no real need to do a VM for that either
docker on windows is in my experience a massive headache, this is only local for development/testing so overhead doesn't matter. In production you likely (hopefully) aren't running win10
Not true. Docker only runs on Linux except if you're running Docker for windows with these gigabyte sized windows images that basically noone uses. Docker Desktop for Windows or MacOS ALWAYS RUNS ON A VM under the hood... Also literally noone wants to "get away from VMs" you run docker on top of VMs the vast majority of times, what docker gives you is a standardized way to deploy and run applications with all their dependencies in the correct versions included in an isolated and especially portable way.
@@meamzcs Ah...the correct dependencies in an isolated and portable way. I'll admit, this sounds great. Lean applications that work!
But then you'll start to think a bit about the consequences of this approach. Unfortunately, with any approach you'll take to to tackle any kind of problem, there will be consequences. Docker (and all other forms of containerization, like flatpak, snap, appimage etc) will introduce more maintenance headache. In every company there is a division between people that are busy doing the new stuff and the rest that are tasked with maintenance of existing (legacy) production software.
Docker is absolutely awesome for the people doing the new stuff. Going for the new stuff is by far more fun and therefore popular with everyone. But for maintenance of (legacy) production software you are creating a lot more maintenance headache. Some legacy production software is locked to certain versions of dll's, libraries and other forms of executable software. Looking for the new stuff is important for future direction of the company. Production software is the lifeblood that provides the income to allow the company to exist. Production software therefore needs to run. Doing maintenance within containers requires much more bandwidth from more people to do correctly. And as this production software really needs to run, maintenance also includes security. Containerization makes this part of maintenance more involved.
Just saw a video from "Dave's Garage", a retired software engineer from Microsoft. He actually tested software performance on bare metal Linux against bare metal Windows against bare metal MacOS. And then repeated these tests with VMs running on these operating systems and then the same test in Docker, running on all operating systems.
In his tests, bare metal Linux won the performance crown. Bare metal Windows was about 2% slower. Bare metal MacOS just below Windows. The same pattern occurred with the same tests in VMs. Virtualization imposed about an extra 3% loss of performance on each OS. With bare metal, you hardly notice the differences, with VMs the drop in performance does become noticeable to those attuned to such things. And then the Docker tests...those introduced a 15% loss in software performance. Anyone notices that, and usually warrants the purchase of a new business class server with proper licensing. Or more monthly subscription costs for (serious) hardware in the Cloud.
The money saved by making the job of the persons involved with the new stuff easier, is doubly spent at the side that provides the company's income. More operational maintenance and costs against convenience. Don't expect Docker (or other containers) to take over from VMs. Containers absolutely have their place and really are interesting as a concept. Definitely more fun than VMs or bare metal. But a replacement? In many cases it isn't, once you'll calculate the actual costs.
A 15% drop of performance with Docker was larger than I expected. Production software that runs at peek performance will generate more income. So that 15% performance drop "bites" the company twice (loss of income and extra costs to make up the lost performance). Have fun selling that in the next budget meeting.
@geroldmanders9742 Not seeing this performance loss you are claiming in my testing
Wow, this cleared up so much! I had a completely cobbled together network config on my docker host. Can't wait to get it cleaned up! Thanks NC!
I try before to run some dockers and i was annoyed but now im more clear about how they works and I dont see that complicated anymore! Thank you!
What a timing! God is so good. This week I was watching the whole networking series because I needed to learn it. Then yesterday I was at the point that I understood much more but couldn’t apply it to docker (where I needed it). And boom. This video came. Gods provision is real! That‘s what I learned again and again. Whenever you do his will and need something, he sees it and hears your prayer. Doesn’t mean that things always come as you‘d wish but as God wants (which is by the way much better!)🥳🙌🏼
I have seen the future: it is filled with Terry Daviw fans and christianity survives posmodernism, becoming a cult-like organization on the internet, programming becomes sacred for them and even thought in our lens they look at least bizarre they will be taken seriously by 2040.
Save this comment..
@@ginbarato1178 Terry Davis*
@@benniferfrost6083 thanks
Chuck gets the credit, not God.
@@testthisfordecficiencies nope, I said what I said :)
God made chuck, he gets the credit 😀
Really useful. I honestly needed layer3 for use with /32 direct routed networks. For a lan it’s extremely powerful. Brilliant video each one of these have use cases depending on where they are applied or what your end goal is. Docker has been stunning with its ability and you’ve explained it great. I’m quite fond of Vlan separation for containers. Hopefully one day Docker will implement a method of doing QnQ vlan trunking
Hi Ven, sorry if this is a dumb question. Do you know a good resource to learn more about networking?
I don't have that background, so after the first 3, things started getting harder to understand
@@R5123 check out Jeremy’s IT Lab on youtube, CCNA series
At 7:27 the bridge data are stored inside a NoSQL database (MongoDB Document model) . It always uses JSON like syntax to store data inside the collection . Amazing
I love your energy in your videos. it makes me get so excited to learn!!!!!
Love ❤️ ur videos best teachers
Thank you!
Love ur videos very encouraging pls keep going making new content
Thank you ❤️
Hi, really good content. May I ask you one use case of the "none" network ?
Not every software you run needs network connections, lets suppose you're running something that just processing files on disk, no network necessary but you still benefit from resource isolation of cgroups.
Such an excellent video. Quick, concise, with examples, no fluff. You could spend a couple of days in a dull class on this or 2h watching this video and stepping through the examples yourself. Thank you!
Thanks for your time.
At 39:11, you wrote 'docker entrork" and it somehow autocorrected to 'docker network'. How did you do it?
By pressing the Tab key
This is probably the best explanation video on docker networks that I've ever seen. Great job!
I might never have understood so much about networking in so little time .. absolutely exceptional, thank you!!
When I started with docker, it was an overwhelming to understand all networking options. This is a great overview and explanation. Nice work.
just the right amount of speed, detail and humour. thanks great video! Feature request: can you put some of the most common video-cli commands into the video notes?
Thanks for putting this together, really helpful..
That video was I needed. A great explanation and easy understandable use cases. Awesome. Thanks for sharing
Thank you for the video. It was due for a long time from me to learn Docker networking and this video helped me!
was fun to watch! thx for sharing
Thanks Chuck for explaining the Docker networking functionality. This is a must watch video for anyone using docker.
Amazing video, I have been using docker for a while now and this is the first video to explain the network types in a way I found engaging. I can't wait to start using some of these networking types in a radio station project I am working on
Thanks for the network diagrams that made the concept very clear. This was very helpful.
Thanks Man! Learned SO MUCH! Always wondered about MACVLAN vs IPVLAN and you nailed it! Awesome video!
I am commenting without completing this video yet... but this is like my best docker networking video yet... after watching that of your buddy you keep bringing up... the animation your video and moving things around nailed it for me... great job ... Thank you so much...
wow!! that was so amazing! thank you! For sure I will practice some more and then add it to my resume!
Sir, thank you for this video! I've been trying to run pi-hole in my setup for months without success, but the explanation in this video made finally do it!
Chuck... Thank you very much for this video. It covers lot of shaded areas I had on Docker networking. You are the man brother.
Thanks ALOT !! I am deploying containers mostly doing copy/paste, now I will understand what I'm doing better !!
I like docker even more now. Thought at first containers where any easy way to setup small vm's or to quickly run programs without having to setup environment/dependences . However this video opens up whole new world of virtualized networking. Great video
Great content thank you !
I've been using the default bridge for years and didn't know the others existed. Thanks for a great overview!
Nice video, thanks and I love your enthusiasm!
This awesome. Thank you for doing it.
Thank you. That was awesome.
Thank you for your classes
Too good , Thanks for all the efforts put in ..Thanks again for all the stuff taught here very very useful ..
This was a great video as I currently have three containers running and was about to build nginx container. I followed someone else instructions and I jacked up their networking instructions where I created a bridge network that went no where. After discovering I could not get the repository open inside Docker. It was more my fault I kind of forgot my IP addressing and subnet binary after not dealing with it routinely for the past 14 years since I retired from my IT position.. Anyway I needed to understand the networking portion better with Docker and you hit the nail on the head! Beautiful, thank you!
Greetings from Ontario Canada! Thank you so much for this video. It has helped me open up my existing dockers to my main network... Something I've been looking to accomplish for some time now.
Thank you so much for this lesson. I'm learning to become cloud engineer rn and This kind of excerpt of key information is what I need! Thank you!
Great tut as usual. Been using Bitdefender for a couple years now, had to reset my two Windoze computers to get rid of Norton. Bitdefender provides a UN-install tool, which is one reason I made the switch. You need a Ember coffee cup. My daughter gave me one for X-mas this year, no more cold coffee for me. Thanks for all the great content, I'm learning a lot, keep it up.
His excitement is contagious. And I barely know anything about networks.
Thank you so much for going so much in depth as I’m a noob with very little experience trying to learn docker.
Awesome! It gives me exactly the knowledge I needed👏
your tutorials are always awesome. detailed explainations and have a real world scenario examples. your helping a lot especially for the beginners. thank you so much...
Amazing video, by far the best one stop shop for a complete (for most use cases) understanding of docker networking.
This was great. You make dense subject matter very approachable. Thanks!