That’s not how that works. network_mode: host shares the network namespace with the container host, so it doesn’t do any NAT, it only exists on the host’s IP. It would be akin to running a natively installed app, rather than in a container. macvlan networking is what gives a container its own IP on the logical network, without the layer of NAT that the default bridge mode networking that docker typically does.
Comment on The Beauty Of Having A Pi-hole · Den Delimarsky
PoopMonster@lemmy.world 3 weeks agoIf your using docker and the ports are bound you can just use the network mode host so the container gets it’s own ip. It’s how I have adguard running on my unraid server
starkzarn@infosec.pub 3 weeks ago
PoopMonster@lemmy.world 3 weeks ago
Thanks for the clarification I had mixed up the details and went to check my containers. You sir are correct. I added some documentation to my post regarding macvlan network creation.
normalexit@lemmy.world 3 weeks ago
Thanks, that’s a good tip!