The Docker Bridge Network - Docker networks part 1
ฝัง
- เผยแพร่เมื่อ 31 ก.ค. 2024
- MANY THANKS TO ALL MY PATRONS on / onemarcfifty !!!
Many thanks for your replies to the poll - your wish is my command and here is the episode on docker networks. As there is so much to tell about docker networks, we will talk about Bridges in this episode. In the next episode we will talk about the host and macvlan network. Networking with Docker, docker bridge networks and docker host and macvlan networks as well as docker-compose are subjects of this series. We will define the networks in the Portainer Networking section
0:00 Intro
1:23 TLDR / TLDW / Chapters
1:42 Describing the setup nginxdemos/hello
2:08 What do we need ?
3:10 Pull the image
4:00 examining the container
5:33 IP Connectivity on the bridge
7:30 Network access
7:55 Hostnames
8:33 Name resolution default bridge
9:22 Port mapping
10:15 The bridge is NAT-ed
11:10 user defined bridges
13:26 Summary bridges
14:00 automate with docker-compose
18:03 Outlook, wrap-up
Here's the list of the commands / steps used in the video:
Portainer Documentation is here: documentation.portainer.io/v2...
sudo apt install docker.io
(on a Pi it may be called docker-ce)
One liner to start portainer:
docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce
(In portainer, click on "Networks" on the left, you'll see the networks)
(on the command line)
docker network ls
(Pulling the image and running it)
docker run -d nginxdemos/hello
(in Portainer, Containers Menu, then "Add Container")
(Finding the IP address - click on the container name in Portainer)
Default Bridge IP is usually 172.17.0.0/24, the docker host is 172.17.0.1
(Click on the container name and Select "Duplicate/Edit" to clone it)
In order to execute shell (/bin/ash) on the command line
docker exec -it CONTAINERNAME /bin/ash
Commands I type INSIDE the containers:
ip addr
hostname
ip route
ping 172.17.0.x
ping 8.8.8.8
ping www.google.com
Create the image with port mapping and container name:
docker run -d --name nginx1 -p 81:80 nginxdemos/hello
docker run -d --name nginx2 -p 82:80 nginxdemos/hello
(now you can browse to localhost:81 or localhost:82)
Create the bridge network:
docker network create -d bridge --subnet 172.172.0.0/24 --gateway 172.172.0.1 --ip-range 172.172.0.128/25 --attachable marcsbridge
In order to run the containers on the user defined bridge:
docker run -d --name nginx1 -p 81:80 --network marcsbridge nginxdemos/hello
docker run -d --name nginx2 -p 82:80 --network marcsbridge nginxdemos/hello
Install docker-compose:
sudo apt install docker-compose
The docker compose file can be found here: github.com/onemarcfifty/docke...
The Microsoft Visual Studio Code Site is here: code.visualstudio.com/Download
(Download the .deb for Ubuntu/Debian, you will then find the File in your Downloads directory. You can then install it with):
sudo dpkg -i (Filename)
for example
sudo dpkg -i code_1.56.0-1620166262_amd64.deb
In order to have the docker-compose extension in Visual Studio Code, select View-Extensions. There are many extensions available, e.g. "Docker Extension Pack" or "Docker Explorer" by Jun Han, or "Docker" by Microsoft or "Docker Compose" by p1c2u
Command line compose up :
docker-compose -f "docker-compose.yml" up -d --build
Please support me on patreon: / onemarcfifty
My youtube channel: / onemarcfifty
Marc on Twitter: / onemarcfifty
Marc on Facebook: / onemarcfifty
Marc on Reddit: / onemarcfifty
Chat with me on Discord: / discord
Licence-free music on / Lizenzfreie Musik von www.terrasound.de/lizenzfreie... music on / Lizenzfreie Musik von www.terrasound.de/lizenzfreie...
The docker logo from Wikimedia Commons By dotCloud, Inc. - File:Docker (container engine) logo.png, Apache License 2.0, commons.wikimedia.org/w/index...
The Thumbnail of this video is under the Apache 2.0 License: www.apache.org/licenses/LICEN... - วิทยาศาสตร์และเทคโนโลยี
I will join the chorus of voices who have stumbled in the dark until discovering your videos. Well done, thank you very much for quality content. I like the pace and the hands-on approach.
Hi Jack, thanks a lot for the friendly feedback - much appreciated ;-)
Incredibly clear information on docker networks. Keep up the great work!
Thank you!
Awesome! I have never come across such a clear explanation on how dockers and docker networks work. Thank you very much
Many thanks for your kind feedback! I am glad you liked it ;-)
After watching other explanations on Docker Bridge Networks and not understanding, this video explains it perfectly !
Excellent
Awesome, many thanks ! I am glad it helped !
So impressed of your way of explain things. Keep up the good work!
Thank you very much!
This is the best docker networking tutorial available in the web. I became a big fan of yours.
Many thanks Krishna!
What a brilliant and nice lesson Marc.
Thanks very much, you are a great teacher and everyone can feel that you put much heart into the lessons.
I hope you continue your muse for a long time.
Happy Weekend :)
Thank you Emilio!
I've just found this channel and I really enjoy every damn video.
Thank you so much!
A firmly handshake from Spain! 🇪🇸
Muchas gracias ;-)
Fantastic Marc….. going to have a play with this, it’s been one of those “dark arts” thank you.
Thank you Tony!
Just waiting for your next episode on this. I love your work Marc 👍👍👍👍
Thank you very much for your kind feedback! I have just published the second episode yesterday - sorry I am a bit short on time these days, so the frequency of videos has gone down a bit - desperately waiting for my summer vacation to catch up here ;-)
I've just started to learn Docker and used this tutorial on an Ubuntu 21.04 VM running on ESXi7. I couldn't believe how much I learned in a very short time!
Thanks, Marc.
Awesome, many thanks for your feedback!
This 2 part tutorial are the first of your videos I watch. I have been self-training in docker for the last few weeks and these are the best introduction to the topic of docker networking I have found by far. Love the hands on approach with exercises that really help get the notions clarified. Bravo! subscribed now.
Hi Cédric, many thanks ;-)
I 2nd this! Thanks!
Amazing tutorial!! I loved the comparison between portainer and the comand line!! Now I have the networking clear!! Thank you
Awesome - many thanks for the feedback. Glad it worked out ;-)
Excellent and to the point, I never used portainer before seems to be a good alternative to the CLI, very good to know and to have it in the bag of management tools. Looking forward to part 2, thank you for the awesome content Marc.
Hi Jairu, yes - I love portainer - I do not necessarily use it to create containers but it's great for everything else ;-)
Great video, cannot wait for the next on macvlan!
Hi Timothy, just published it yesterday ;-)
legend. great level of detail, welll explained. love your work
Thank you!
Thank you Marc - very informative and well-presented.
Thank you very much David!
Well done! I enjoyed watching it, learned new things as well.
Hi Filip, many thanks !
Thank you. I have been wondering how networking worked in Docker. I learned so much.
Many thanks for your feed back Mike !!!
really enjoyed watching this one. having spent a couple of weeks clicking around in portainer and not being quite sure how the interface & the options dovetail with docker input on the CLI or using docker-compose, this clearly explained and engaging video has helped tremendously to demystify. And i also learned some of the fundamentals of docker networking also.
when at first a topic seems unfathomable, there is a sudden lightbulb-moment when it all begins to make sense. the demystification process (the rolling back of the fog) is to a greater extent attributable of the abilities of teacher. i'm guessing you are a teacher by profession (?). Many thanks Marc for the time and effort you have put into sharing your knowledge. without hesitation, i have subscribed.
Hi, first off many thanks for your feedback and for subscribing! No, I am not a teacher ;-) I work as a Presales consultant for a software vendor ;-)
You are the best instructor! thanx for you work!
Thank you very much ;-)
This was very instructive and easy to follow. Thank you.
Thanks a lot;-)
how nicely you put topics thanks.
Thank you very much!
Very informative, thank you. There are far too many videos out there that are just like "use host" or "use bridge" and never explain why. Then if things don't work you're left on your own to figure it out with no real understanding of what is going on.
Hi Lee, many thanks for your feedback. there's more on my channel page th-cam.com/channels/G5Ph9Mm6UEQLJJ-kGIC2AQ.html
Great video, very well explained. Thank you.
Thank you very much !
Really liked the way you described. Keep it up
Thank you
Great tutorial! Many thanks!!
Thank you very much!
Excellent tutorials ! - Thank you ! "Keep on movin !"
Thank you - I will ;-)
@@OneMarcFifty Das freut mich. Um gute Tutorials zu produzieren muss man die Materie beherrschen und in der Lage sein "Verständnishürden" zu erkennen und. zu kompensieren. Das gelingt Dir hervorragend.
Cool, danke !
Thanks for explaining all of this
Thank you!
This was brilliant, thanks!
Many thanks Dylan!
very clear, well done, thanks!
Thank you !
Amazing content, thank you
Hi Aleksei, thank you very much!
this is just perfect thank you
Thank you Etienne
Thanks for videos. It explained a lot
Thank you
Docker network Macvlan, docker-compose, and mptcp server would be an amazing project to see.
The second episode has just been published yesterday ;-)
thanks and keep creating !
Will do 😉
Great start to the series
Thank you !
Thank you for your video
You’re welcome 😉
darauf habe ich gewartet..
Hey Tom, awesome - I just published the second part yesterday ;-)
sick content bro :D thx
May I take this as a compliment?
@@OneMarcFifty ofc 😊
Very interesting
Thank you.
you should have more subscribers
Thank you very much Chris ;-)
Excelent
Thank you!
Great one. Any change to go over the question with rancher ? Keeping the socket open behind the loadbalance for docker networks ?
Thank you Erdem. Time is a bit of a constraint at the moment - still answering messages from the last 4 weeks ;-(
I did the same steps on Windows 10 host, the IP address of the first container "172.17.0.4", doesn't show anything in the browser.
Ah - not sure about Windows here - the ip addresses might be different
Mark... this TH-cam/dudes won't let me like this video more than once... 😁 you must fix this!!!
,,, so... you get the 'cryptic' hostname and then ping the 'friendly' name... 😶🌫
this way you confuse the audience...
you should had ping the 'cryptic'... and pointed the ip,,,
and next ping the the 'friendly'... and alert you go the same ip...
;-)
Haha ;-) Thanks mate - and thanks for the advice ;-)
Thanks for the wonderful explanation. However @4.44 I didn't get any response after hitting the ip of the container through browser. Not sure why so.
Did you try and access it from another machine or locally on the docker host ? this only works on the machine itself.
Great video and good information.
I have one question. I have docker on my raspberry installed.
When i install Visual Studio Code on my computer, how do i connect to the raspberry docker instance?
Hi, I am not sure if that is possible. Have you checked the Extensions page of Visual Studio Code ? The way I use the docker extension is that I test docker on my local system and once everything is OK I transfer the files. So I do not do in-place editing on the host.
On "Compose Up" from vscode I got the error:
"ERROR: Couldn't connect to Docker daemon - you might need to run docker-machine start default."
After a while I managed to compose up from a terminal: "docker-compose -f "docker-compose.yml" up -d --build".
Two containers were created which I could check with the terminal command "sudo docker container ls".
Both work fine and I can reach them from a web browser, but I cannot see newly created containers in portainer.
By the way the terminal command "sudo docker container ls" shows me only the containers created from the terminal, but not the containers created from portainer including the portainer itself.
Now that's interesting. Are you sure that you are connecting to the same docker instance with Portainer and the local docker ? Portainer created containers should show up just like normal containers. They are no different. Maybe try docker container ls -a in order to see all of them, including the ones that are not running ?
if the host IP is 172.17.0.1, and there is another machine on the same network with IP 172.17.0.2, then how could the host create a container with IP 172.17.0.2 inside the host itself? Wouldn't the host get confused with the two entities?
It depends on the routes that are set up on the host and which network adapter the IP is bound to.
do you have experience with separate network in k8s clusters between namespaces ?
Hi P S , no not really, I havent done much with Kubernetes.Pure Docker for the time being. Sorry ;-)
Hello there ! Thank you for providing us with a great video again !!!
I would like to ask a question though. If you have a file for example a .txt and you want to create a parser with a python container. How is it possible for the container to see and edit the file that is located in the linux OS outside the container ??
I'm new to docker and containers sorry for my newbish question :)
Hi - typically you would either have the file in a docker volume (i.e. docker volume create xxxx) and attach it to the container or just attach it with -v as a bind mount. Like docker run -v /data:./data
@@OneMarcFifty Thank you Marc, that's enough info in order for me to search more stuff and try asap the above suggested :)
For the ip range should it be 172.172.0.0/25 for the first half i.e. 172.172.0.0 to 172.172.0.126?
Hi, could you give a reference / time marker or a context please of what you want to achieve?
@@OneMarcFifty Hi, at around 11:44
You say bridge network ips are accessible from outsite yet with the ip numbers on browser you accessed first two containers you deployed
Hi - very well observed ;-) Yes, the container is not accessible from outside _the docker host_ but in this video docker is running directly on my workstation, hence I can access it from the local host.
@@OneMarcFifty thanks for clarification. In my first comment a “not” is missing (not accessible) even though you understood me the way I meant. I like our host’s engineering manner. Thanks as always
Schade das es das Video nicht in deutsch gibt
Hallo Robert - ja, TH-cam unterstützt leider keine mehrfachen Audio- Spuren. Ich lade aber zu allen Videos die Text-Daten hoch, so daß die automatisch übersetzten Untertitel ziemlich akkurat sein sollten.
@@OneMarcFifty vielen Dank für deine schnelle Antwort. Hab mir gerade angesehen, leider kann ich den Untertitel nur in Englisch auswählen. Mache ich da etwas falsch?
Hmmmm…. Geht tatsächlich auf dem Handy nicht - ich probiere es gleich auf dem PC - wenn’s da auch nicht geht habe ich vielleicht vergessen einen Haken zu setzen irgendwo - ich melde mich nochmal
OK ich hab das jetzt mal getestet - das Feature ist tatsächlich nur im Browser verfügbar, nicht in der TH-cam App ;-( Ich muss mal überlegen, ob ich für die "wichtigsten" Sprachen vor-übersetzte Untertitel anbieten kann (EN/DE/FR/ES/IT).
@@OneMarcFifty danke für deine Mühe. Hab's im Browser aber auch nicht hinbekommen, hab bei Untertitel da als Sprache auch nur Englisch zur Auswahl.
A minute and a half, I shut it off Because you haven’t told me anything
Hi Hugh, first off - many thanks for the honest feedback- I do appreciate it! Let me watch the video again and I‘ll come back to you. Maybe I was too long on the intro.
You lost me at Microsoft. It's unnecessary.
Well - I understand Microsoft is kind of a no go to many in the Linux community. But I actually do like VS Code - Which IDE are you using ?
I could not get it to work on WSL when I went to the IP address at 172.17.0.x
I haven't tested this on WSL - might have a different IP there or maybe the Windows Firewall m*sses things up ?