I followed this guide and entered this command: docker network create -d macvlan -o parent=eth0 \Īttach the network and it's done! The container is part of the outside network. So any help getting me on track with this issue would be greatly appreciated.įor anyone else including my future self that comes across this post this is what i did. I feel like I've tried everything that makes sense to me and when i google for more answers it seems like either nobody gets a solution or they get some solution that doesn't work for my needs ( like exposing a port on a different ip address). Obviously this only exposes the containers ports on a different ip address so its still pulling internet out of dockers internal bridge. I tried to assign the ip address manually in the port part of configuration like so: I tried to create a linux bridge using this guide but docker wouldn't fully start afterwards when I tried to add the config into my startup. Either the container wouldn't start or it wouldn't get internet. The communication would be established only if the bridge network is provided and the proper permissions on the iptables rules are given.
#Docker network host vs bridge driver
I have tried to create a new custom docker bridge that uses my network's ip addresses. The Docker bridge driver automatically installs rules in the host machine so that containers on different bridge networks cannot communicate directly with each other. I understand I can build my own container with an inbuilt vpn but my vpn provider doesn't assign me anymore than 5 connections that I already am actively using. Also, I cant vpn the entire host because i have containers that need to be public facing. I have a Pfsense router that gets specific ip's within the subnet and vpn's them. I want docker bridge a docker container to the external network like virtualbox would when you use the bridge option.
0 kommentar(er)
