[x] I searched existing issues before opening this one
Expected behavior
dockerd have switch to re-create iptables rules without restarting docker deamon itself. Majority of firewall scripts does flush all rules prior to re-applaying themselves, meaning every time such script is updated and executed, Docker looses access to the network. It would be great it such scripts could poke dockerd with for example --only-iptables-restore to minimize the effect on Docker containers.
Actual behavior
in order to restore iptables rules, docker deamon has to be restarted
Steps to reproduce the behavior
Client:
Version: 18.05.0-ce
API version: 1.37
Go version: go1.10.3
Git commit: f150324
Built: Thu Jul 12 10:47:14 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.05.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.10.3
Git commit: f150324
Built: Thu Jul 12 10:46:31 2018
OS/Arch: linux/amd64
Experimental: false
Expected behavior
dockerd
have switch to re-create iptables rules without restarting docker deamon itself. Majority of firewall scripts does flush all rules prior to re-applaying themselves, meaning every time such script is updated and executed, Docker looses access to the network. It would be great it such scripts could pokedockerd
with for example--only-iptables-restore
to minimize the effect on Docker containers.Actual behavior
in order to restore iptables rules, docker deamon has to be restarted
Steps to reproduce the behavior
Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)