Here is a sample dmesg:
88674.465534] br-9fdcd69e27e2: port 18(veth9ad5d51) entered blocking state
[88674.465539] br-9fdcd69e27e2: port 18(veth9ad5d51) entered forwarding state
[88674.581288] br-b2bf533d47a1: port 11(veth343a11a) entered blocking state
[88674.581295] br-b2bf533d47a1: port 11(veth343a11a) entered disabled state
[88674.582151] veth343a11a: entered allmulticast mode
[88674.582237] veth343a11a: entered promiscuous mode
[88674.583262] eth2: renamed from vethedaec20
[88674.597359] br-b2bf533d47a1: port 10(veth3ba0176) entered blocking state
[88674.597373] br-b2bf533d47a1: port 10(veth3ba0176) entered forwarding state
[88674.602520] eth2: renamed from veth3e0eb3f
[88674.615183] br-b2bf533d47a1: port 11(veth343a11a) entered blocking state
[88674.615194] br-b2bf533d47a1: port 11(veth343a11a) entered forwarding state
That is just a sign of restarting containers. Have you checked container statuses and logs? docker ps should show if some containers are restarting. At least you can see since how long it is up. And docker logs containername can show you if the process inside the container stopped.
I am not sure about “disconnected iptables”. I have never seen that in error messages.
But IAs @bluepuma77 pointed out, your Docker is pretty old. It could be incompatible with the latest Ubuntu versions, I am not sure. And the chance of incompatibility is increasing with every package upgrade on the OS.