I just learned: Docker edits firewall rules for you
geoff.tuxpup.com
I just learned: Docker edits firewall rules for you
1–10 of 126 posts
Re: I just learned: Docker edits firewall rules for you
#2K8s at least offers more fine-grained control over networking, between port range restrictions and having to enable a NodePort.
Re: I just learned: Docker edits firewall rules for you
#3If he'd bind the host port to localhost or put caddy in a container in the same vlan, it wouldn't have happened. From the blogpost I'm not even sure if he's aware of the binding option.
If you argue that a software shouldn't behave this way after being configured so explicitly, Archlinux not preconfiguring iptables to limit exposure like Debian or Ubuntu is worse, because it happens implicitly.
Re: I just learned: Docker edits firewall rules for you
#4(Yes yes I know iptables is antiquated but they should still be compatible with each other at the kernel level)
Re: I just learned: Docker edits firewall rules for you
#5I came up with some rules including DOCKER-USER chain but I'd qualify them as hack relying on undocumented configuration. And I just have no idea how to configure firewalld because it puts another layer of complexity on top of iptables.
Re: I just learned: Docker edits firewall rules for you
#6Re: I just learned: Docker edits firewall rules for you
#7Re: I just learned: Docker edits firewall rules for you
#8Re: I just learned: Docker edits firewall rules for you
#9Re: I just learned: Docker edits firewall rules for you
#10You can also add `iptables: false` to docker's daemon json and docker will stop messing with your iptables conf.