The Docker HOST and MACVLAN Networks - Docker Networks part 2

Marc: I just discovered you videos on Docker Networking. I must say they are the best I have seen yet. I have been using Portainer for several years now and yours is the first docker networking videos that actually use Portainer. Thanks for that. I am disappointed however, that I don't see any videos on IPVLAN's. Are you planning on doing videos on ipvlanL2 and ipvlanl3. I think you would do an excellent job!! Thanks again.

I've been fighting with this for 2 full days. Thank you, Thank you. Now I have the application that "HAS" to be on the same network as the host, there on a macvlan, and the other containers on a local bridge network they share with that app.

will you make videos about differences between ipvlan and macvlan in docker networking?

Great video! Have any command to notify the router about the macvlan created with specific ip?

Hi Marc,

Thank you for your wonderful tutorials, you have a great way of explaning things clearly!

I have also been following the OpenWRT VLAN tutorials and, as I am running Docker on OpenWRT (on a NanoPi R5S), I wondered whether you would cosider doing a tutorial about that?
Specifically how the networking in Docker relates to the VLANs in OpenWRT. At the moment, my Docker containers are accessible from all VLANs and I don't fully understand why and how to make Docker 'VLAN aware'?

Anyway, thanks again for making these and sharing with us
👍

"Ózóne"... Marc... let's go to the import of a vhd(x) to inside a container... ;-)

This video material should be on the official docker documentation website

I just want to be able to have static ips in my lan by mapping mac to ip once router dhcp gives ip... but of course portainer makes this wonky for me...thanks for great video i will need to figure out a subnet solution.... UGH, why is this so hard i thought having docker container as static IP on LAN would be easy since many used that... but nope, so close, but no cigar...

keep it going my dude, networking is one of the most difficult things for me to grasp when it comes to docker/portainer

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.

You have saved me, I have tried all the google tutorials online. But terminal did not work to enable access from other non docker machines on my network to my macvlan container. Thank you so much 🙏

Nice. Thank you & team for the efforts

Fantastic, it will be great to know more about the docker-compose features as it seems like a way to automate the deployment of the docker images. I also agree with creating a tutorial using two different physical hosts, docker hosts, and take it to the next level by simulating a larger project of containers. Thank you very much Marc! all the very best and until the next one.

Thank you very much , a lot of info , please more videos on Firewall for docker networking and docker swarm

Hi,thanks for thé video.
When I do the dhcpcd interface name
It says interface not found or invalid dhcpcd exited
My interface is enp0s31f6 and it is the same interface on my host machine with ubuntu 18.04.
What could be the problem please

Did you end up making a video showing how to import a disk image in a docker container?

I would love to know the reason portainer requires these 'config' macvlan networks. Does it provide any benefit or is it just to work around some issue integrating with Docker?

Btw, when setting up the macvlan network you said that you configured an ip range that has nothing to do with your LAN but it was within the same subnet so I did I miss something? Honestly I don't understand what the purpose of the IP Range is since it doesn't seem to be possible to define an arbitrary range and I couldn't subsequently create the actual macvlan network unless the gateway address was within the 'IP range', even though the gateway address was within the subnet.

I would like to see comparison of macvlan vs. ipvlan networks in docker, and some practical examples of each. Thanks again for your terrific videos!

Marc, I really like your videos. But! I have a problem when it comes to get an IP with DHCPCD every time and I went through that section over and over again but with the same results: 
dhcpcd eth0
eth0: if_init: Read-only file system
eth0: interface not found or invalid
dhcpcd exited
I can't understand what I'm missing here. Please advice if you can.

Hey, would like to know what OS you're using for this demo?

Very useful, please do how to make firewall containers

Macvlan is supported on cloud instances ex: aws?

I would like to thank you for this very useful video and wish you good luck in your future work.

Hi Marc. Pretty late to the party but ran into a couple of problems with some of the steps in the video whose content I would say is excellent! I am running Docker in VirtualBox on Windows 10 with the adapter in bridged mode. I never was able to resolve the address of client on the Docker container in bridged mode when doing iperf3 -c <docker bridged ip address>. I also never was able to get Docker container to be able to ping an address on the macvlan even after successfully getting a DHCP address from my DHCP server even though the VirtualBox adapter was bridged and set to promiscuous mode. Any thoughts or pointers to where I might be able to resolve these two problems?

I would have liked to see how to connect to the containers from the host using macvlan, but I can understand that it was getting off topic.

Marc, thank you for amazing videos that you have made! you made me make my home network a better place for my family :). One question on the topic of this section.
After I restart the container, the ip address of the eth.x interface is back from the DHCPCD to the MACVLAN that we have created for local use. Do you know if there is a way to set it up so that the machine would always get the Primary LAN ip address? Thanks!

I liked the video, very informative. But in the video you mentioned about setting a defined mac address for the container, and you don't show how to do that... Such a missed opportunity. You should at least post the commands in the video description.

I love your tutorials, thanks a lot from Enschede NL !!!

great 👍 thank you 😊

what if i want to use a socks5 proxy to route certain machines from a lan on one subnet through a different gateway on another subnet that only my router-server is connected to via its two nics? how would i go about doing that with docker?

Thank You. Your way of explanation make me docker networking more interesting.When could we expect more videos about docker swarm with two ore more hosts and overlay and ingress networks?
Great content that we cannot find anywhere else.

macvlan did not work for me.

Great job. great content that you can't find maybe anywhere else; because he's mixing something enthusiastic with something scientific.

awesome !!

You have discussed a very useful capability of a docker host/container in MACVLAN... I have not found this searching many tutorials in which I am sure there should be... Imagine a docker firewall inside a host, with all packets passing thru and processed by the docker firewall; even the host should use the guest docker firewall as its gateway to the outside world.

The security possibilities will be endless in this arrangement, as all services can be made to only have a bridge internal IP, all using the docker firewall. ALL as in all packets inisde or outside should be made to pass only thru the firewall. Since this firewall is a docker instance, everything will be very flexible, easy and secure.

That is why I have searched for this docker capability, MACVLAN will make this possible.

Thank you for your good and clear overview. God bless.

Awesome Tutorials, learned a lot in Part 1 and had my head explode in Part 2 :'D. Could you possibly create a tutorial, how to create and configure the docker networks correctly, so you could expose services run in docker to the outside world (ideally with a domain) - so basicly including portforwarding and a reverse proxy?

I am mainly asking because I have a slight Network related issue or I believe it is. I have 2 physical devices behind my router, that I both want to expose to the internet. One is a Synology-NAS and the other being a NUC-Server with Ubuntu, Docker, Webmin installed (from your other Tutorial). What I'm currently trying is to use nginx or traefik to forward the incoming requests for services run on the NUC-Server correctly. However I might have understood something wrong how to configure the ports in my router or in the docker networks. Right now I have port 80/443 opened which point to my NUC, where I also run nginx reverse proxy and I'm trying to point to various services and the NAS as well. However I really never got everything to work and maybe a tutorial would help.

Appreciate your tutorials, because they are well structured and very thought through! Thanks

Usualy I don't hit the subscribe button very fast, but in this case 2 out of 2 videos where just amazingliy good. Thanks for this easy understandable video with with comprehensible examples!

WOW!! Looked for promox and looked for hours!! Very good job, thank you!!
Many questions but have to get new hardware first to install proxmox.
First to ask is: can you convert a running metal machine and convert it into a virtual machine? Very curious in this item!

Yes, I still use VMWare where 9 servers are running for long time. Also use Parallels on MAC and Virtual box for testing. I was Novell guy since 3.11 (1988) and grew along till 2008. Then changed job and country and got never really back into networks. Too bad, miss it! Time to retire soon and get back into networks and pick up some programming!

A testbed of OpenWrt on docker would be great...

Great video, thank you!

Really excellent videos - I finally think I'm getting to understand docker networking! I find your explanations and demos very clear (even if I have to watch them a few times). There were a couple of comments about you going too fast, I have to say I didn't find that: I stop try what you've suggested and replay - that works for me.

Hello Marc. Nice two videos for newbies on docker. Keep it up. When possible do OpenWRT on docker with adblock and setup as a gateway pc.

Hi, ich habe gesehen, dass du da openwrt als Container hast. Kannst du dazu ein Video machen? Ich bekomme das leider einfach nicht zum laufen...

Another great video! Thank you for the useful content and keep up the good work. I would love to see more docker networking as well as security. Would be great to see how to segregate services and and access control.

Really like the way you described it. But frankly while demonstrating, your pace is too fast. Please keep your pace slow, and explain it a little further in-depth.

Thanks for the great video! Considering all of the lately topics, have you considered a video on how to configure two routers for high availability? I think it would be useful when having your main router as а VM in Proxmox configured with a backup router when updating the Proxmox host or during debugging.

Nice

Of course yes! We are all interested into your next docker networking video!!

thanks for the video! very useful and easy to follow for someone just starting out