> No they shouldn't, just how nginx shouldn't manipulate iptables just because you've said it should listen to 443 on "the network". But you've typed in a com

> No they shouldn't, just how nginx shouldn't manipulate iptables just because you've said it should listen to 443 on "the network". But you've typed in a command that explicitly will alter the iptables rules, as documented, and as you have requested > Many times you don't even want docker containers to go "to the network" directly and it shouldn't assume unsecure behaviour by default. Docker containers do not have a network connection outside their own subnet by default, and only expose the ports that they have explicitly been configured in the Dockerfile to expose. By determining the container's IP address you can talk to it directly but this is not really recommended, because it can and will change. This internal IP address is by default in an RFC1918 range, and will not be in any way accessible from the outside world. > Moreover, CRITICALLY, you can't prevent Docker from doing that and you can ONLY secure the machine by adding another rule on top that supresses Dockers rule... and those dockers rule change over time making it easy for the blocking hack to stop working after an update and again make the machine unsecure. You can prevent Docker from doing that, by not adding into the command line the additional option that tells it to hook containers up directly to the "outside world" interface bypassing any firewall you might set.