Docker Networking Tutorial, ALL Network Types explained!

Docker Networking Tutorial, ALL Network Types explained!

Christian Lempa

2 года назад

194,211 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

Erick W
Erick W - 01.10.2023 23:43

Earned a subscriber with this one!! This helped me fix my Docker home assistant network problem!

Ответить
Max Bruce
Max Bruce - 26.09.2023 06:10

Too fast

Ответить
zhitoo
zhitoo - 21.09.2023 20:33

short, useful , great, awesome thanks alot

Ответить
RUPAM MANDAL
RUPAM MANDAL - 11.09.2023 15:50

A couldn't connect to the IP of a macvlan container from the same machine in which the docker is hosted. However it can be accessed from other machines in the network. Is there anything that can be done?

Ответить
Yaroslav Ozerov
Yaroslav Ozerov - 30.08.2023 23:17

Bro! Thanks for the video, but the biggest thanks for picture on your t-shirt! I had such poster on my wall in 90th! That's awsome))

Ответить
Chinyere Onyenwe
Chinyere Onyenwe - 09.08.2023 02:58

kinda hard to understand with the speed you re going.

Ответить
AnythingGodamnit
AnythingGodamnit - 05.08.2023 05:18

Loved this, thank you. I now feel like I have the knowledge to solve my current Docker networking problem - excited to try!

Ответить
rshn thms
rshn thms - 01.08.2023 22:49

Can this fix below problems,

How have docker without docker desktop so that I have 2 containers service [django and nginx] which share a network also in the host [wsl2 Ubuntu] mysql is installed.

How to connect django and mysql, django and nginx?

Does macvlan or ipvlan slove it?

Ответить
Ghost kee
Ghost kee - 30.07.2023 13:49

bro is literally talking so fast like a machine without a pause and without using any schemas or figures to explain!

Ответить
Douglas Sousa
Douglas Sousa - 15.07.2023 23:50

Tu e o cara cuzão

Ответить
R K
R K - 15.07.2023 23:00

which means that by default containers arent secure.

Ответить
Lory l
Lory l - 29.06.2023 22:21

It seems macvlan work proprely on wired interfaces .With wireless interfaces it is more complicated

Ответить
S BA
S BA - 16.06.2023 15:38

Finally somebody who explains that stuff clearly and without jargon! Thank you so much for your contributation!

Ответить
James Hertz
James Hertz - 10.06.2023 12:06

I use docker swarm because I need to do experments :c

Ответить
sebastian posada
sebastian posada - 31.05.2023 19:36

Im having an issue with the macvlan. I can ping the containers from my home computer but i cant get a response from the gateway. I am running virtual box for my machine and i have promiscuous mode on. I have been troubleshooting but cant seem to get it to have connectivity to outside the network

Ответить
stoic
stoic - 23.05.2023 20:29

who uses docker swarm ....

Only the reason i watched the entire video waiting for overlay networks :(

Ответить
P. Alejandro Alandia
P. Alejandro Alandia - 19.05.2023 19:39

Amazing explanation thanks

Ответить
Abreu
Abreu - 02.05.2023 22:15

I spent probably 3h figuring out how to assign another external IP to a Bind9 container, doing a lot of research and trying with ChatGPT.
Found your video, solved in 5min !!!

Ответить
Nicola Dellino
Nicola Dellino - 20.04.2023 18:29

Very nice video, THX.

Ответить
Eratz
Eratz - 20.04.2023 12:45

Thx macvlan is what i needed for some containers

Ответить
Andrew Ochoa
Andrew Ochoa - 11.04.2023 17:53

Thanks for the insight on the various network drivers on docker. I blindly used a macvlan from a tutorial for pihole but wanted to understand how it works.

Ответить
David Something
David Something - 09.04.2023 13:29

Just getting started with docker and loving it. One thing I am struggling with is getting IPvLAN L2 working with fixed IP addresses through compose when the ipvlan already exists on the host, jus seem to get one error after another when specifying the existing network. I've got multiple USB interfaces on a debian instance loaded on a PC and am using IPvLAN as alternative to macvlan and having to setup promiscuous mode although I have macvlan 802.1q working on another host so I have no issue with the concept and have a good understanding of networking as a whole. I've setup an ipvlan with fixed addresses for a ipam container with a separate container for the database and this works no problem but I had to setup the containers the old fashioned way.

Ответить
R1D9M8B4
R1D9M8B4 - 09.04.2023 01:45

I like you.. I had this question... like.. a week ago.. the algorithm is late..

Ответить
Zack
Zack - 24.03.2023 02:49

setting up an reverse proxy is easy enough, but how do you setup "client-containers" behind the proxy that can only access the outside though the proxy?
I guess if you set up the other containers on the same network as the proxy or an vlan network, they have direct access to the outside network

If this was physical machines or VMs, I would just have put 2NICs on the proxy machine but no clue if this is possible on dockers or if that is how you do it

Ответить
John Slegers
John Slegers - 10.03.2023 10:31

Thank you Christian for this great explanation. I do have a question is it possible to have a container in two networks? I'm trying to create a compose file with PiHole and Unbound. The Pihole has a macvlan for my network and also a bridge to communicate to unbound. But every time I want to compose it the bridge network on the PiHole gives an error Cannot start service pihole: No available addresses on this pool. IS it even possible to create a container in two different networks?

Ответить
Oppai Lover
Oppai Lover - 08.03.2023 04:20

Thank You man! I was just randomly watching this video and figured out how to solve port 53 issue for pi-hole in docker

Ответить
mal-avcisi
mal-avcisi - 24.02.2023 11:09

this guy knows his shiat. bravo !

Ответить
Jay P
Jay P - 20.02.2023 15:50

Incredible video. I’m currently binge watching your channel and I’m amazed by the the quality of all your content. Keep it going man, you are great!

Ответить
sbkpilot11
sbkpilot11 - 16.02.2023 06:01

Great video! One thing I noticed is that in WSL2 with Docker Desktop the behavior is rather different - when you create a new bridge network there is no interface created. I wonder how it works in this case.

Ответить
Franco Castillo
Franco Castillo - 10.02.2023 04:42

The most important thing you have not explained: how to connect the host to the containers that use macvlan and vice versa.

Ответить
Alejandro Rodriguez
Alejandro Rodriguez - 07.02.2023 21:14

wonderful work

Ответить
دنیای آینده
دنیای آینده - 31.01.2023 02:59

You're wonderful 👍

Ответить
𝐓𝐆𝐢 𝐆𝐚𝐦𝐢𝐧𝐠 𝐘𝐓
𝐓𝐆𝐢 𝐆𝐚𝐦𝐢𝐧𝐠 𝐘𝐓 - 14.01.2023 11:02

Could you please make video on installing Adguard home in NAS. I am running issue when macvlan is assigned. Cannot able to ping NAS or adguard home container in docker.

Ответить
Lucio
Lucio - 11.01.2023 20:14

Reasons to use docker swarm instead of kube in a small-home-cluster:
- you don't want to turn swap off on your nodes, because you need it for other stuff
- you have already a bunch of stacks in docker-compose files and you're not up to the chore of converting them all on kube pods
- you have a bunch of raspberryπs in your cluster
- you want to put homeassistant with all its bits and bobs on a cluster, and you failed when you tried to do the same thing with kube (😆ok this might be very specific to me)

None of these reasons are ofcourse valid for a "real" production environment.

Ответить
Fabiano Chagas
Fabiano Chagas - 12.12.2022 17:00

Awesome as always! Thanks for sharing

Ответить
Paul Kalus
Paul Kalus - 04.12.2022 23:22

Hi Cristian, this is a another great video. The Macvlan part is something I've been searching and searching for, always coming to a dead end. The way you have explained and demonstrated it is spot on and has solved my issues, and I've actually learned something! :)

Ответить
1007_ Dhruv
1007_ Dhruv - 28.11.2022 11:55

Could someone tell me how to create a custom bridge network in an AWS ECS task definition, without using docker-compose?

Ответить
Thulasiramteja !
Thulasiramteja ! - 20.11.2022 10:07

Hello,
i had facing macvlan problem for 2 days in centos 8. when i specified the macvlan network with a container attaching to it and when i exec the container tried to ping host its not working. but outside the container ping works.
in centos 7 i added "sudo ip link set enp0s3 promisc on " and tried again ping inside the container it worked. but in centos 8 or ubuntu 22.04 the above command didn't work. please help me to get away from this issue.

Ответить
NEED5
NEED5 - 16.11.2022 17:36

How to stream iptv channels using server and get url link Nginx ? just for learn

Ответить
Alessio Rossini
Alessio Rossini - 09.11.2022 01:15

even if the video is 1 year old it made my day!!! Thanks Chris very clear and well done

Ответить
Johnny T
Johnny T - 19.10.2022 22:57

Really informative. Just stumbled on to your channel. Fast paced and great information. Just managed to keep up as I'm completely new to docker. Subscribed to your channel. Thanks 🙂

Ответить
LAEL A.H.
LAEL A.H. - 17.10.2022 17:58

How can I make my container use a specific interface on a host system i.e. I have one cable connection and two wlan interfaces and I've got 3 containers. I'd like each to use a dedicated interface. Which type of network will be best and how would I go about it?

Ответить
Michael Kane
Michael Kane - 17.10.2022 17:13

Interesting! What type of network should I use for my home server setup and run containers behind wireguard client for my torrenting?

Ответить
Yaser Ghananwi
Yaser Ghananwi - 15.10.2022 12:31

Hi
nice tutorial , i true to check network interface but there is no docker0 bridge on macOS
BR

Ответить
Thomas Tobias Conrad
Thomas Tobias Conrad - 14.10.2022 12:13

If you create a mcvlan and attach a container, the Host no longer can access the container, but all clients on your network can. I had to create a bridge for the macvlan and specify the ip routes for the host to that container.
I encountert this problem as I deployed pi-hole in my network, and specified in the settings of my DSL-router this pi-hole container as a network wide DNS-Server.
All clients were able to resolve the new DNS-Server, but the rest of the docker containers and the docker host himself were no longer able to reach this IP (even though they were on the same subnet), so the host was not able to perform updates anymore (no DNS resolution).
Is there a 'nice and shiny' solution I didn't catch, a better way to solve this issue or a best practise way to handle those kinds network things? What would be your attempt?

Ответить
Pierre R
Pierre R - 04.10.2022 17:56

Thanks ! Great explanations. Have a nice day

Ответить
Ellyll
Ellyll - 02.10.2022 13:05

This video was really helpful for me to get a nice quick understanding of docker networking, thank you!

Ответить
cool glass
cool glass - 28.09.2022 20:10

Great videos dude! can i ask why Owasp says we should set ICC to false? I am guessing they just mean they want us to use custom networks?

Ответить
kelei tangpusen
kelei tangpusen - 26.09.2022 10:50

Hi, can macvlan take effect in the virtual machine, after I configure macvlan in the VMware virtual machine, the container cannot ping any ip or even the host

Ответить