Комментарии:
Earned a subscriber with this one!! This helped me fix my Docker home assistant network problem!
ОтветитьToo fast
Ответитьshort, useful , great, awesome thanks alot
Ответить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?
Ответить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))
Ответитьkinda hard to understand with the speed you re going.
ОтветитьLoved this, thank you. I now feel like I have the knowledge to solve my current Docker networking problem - excited to try!
Ответить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?
bro is literally talking so fast like a machine without a pause and without using any schemas or figures to explain!
ОтветитьTu e o cara cuzão
Ответитьwhich means that by default containers arent secure.
ОтветитьIt seems macvlan work proprely on wired interfaces .With wireless interfaces it is more complicated
ОтветитьFinally somebody who explains that stuff clearly and without jargon! Thank you so much for your contributation!
ОтветитьI use docker swarm because I need to do experments :c
Ответить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
Ответитьwho uses docker swarm ....
Only the reason i watched the entire video waiting for overlay networks :(
Amazing explanation thanks
Ответить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 !!!
Very nice video, THX.
ОтветитьThx macvlan is what i needed for some containers
Ответить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.
Ответить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.
ОтветитьI like you.. I had this question... like.. a week ago.. the algorithm is late..
Ответить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
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?
ОтветитьThank You man! I was just randomly watching this video and figured out how to solve port 53 issue for pi-hole in docker
Ответитьthis guy knows his shiat. bravo !
Ответить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!
Ответить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.
ОтветитьThe most important thing you have not explained: how to connect the host to the containers that use macvlan and vice versa.
Ответитьwonderful work
ОтветитьYou're wonderful 👍
Ответить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.
Ответить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.
Awesome as always! Thanks for sharing
Ответить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! :)
ОтветитьCould someone tell me how to create a custom bridge network in an AWS ECS task definition, without using docker-compose?
Ответить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.
How to stream iptv channels using server and get url link Nginx ? just for learn
Ответитьeven if the video is 1 year old it made my day!!! Thanks Chris very clear and well done
Ответить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 🙂
Ответить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?
ОтветитьInteresting! What type of network should I use for my home server setup and run containers behind wireguard client for my torrenting?
ОтветитьHi
nice tutorial , i true to check network interface but there is no docker0 bridge on macOS
BR
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?
Thanks ! Great explanations. Have a nice day
ОтветитьThis video was really helpful for me to get a nice quick understanding of docker networking, thank you!
Ответить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?
Ответить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
Ответить