On Mon, 29 Apr 2019 07:46:22 +0700 Arnaud Rebillout <arnaud.rebill...@collabora.com> wrote: > Actually this was fixed upstream lately, and the fix is in Debian > testing already. See > https://github.com/docker/libnetwork/pull/2339#issuecomment-487207550 > > There's still other iptables related bugs, the most outstanding being > #903635. If this bug could be solved, then users could just run docker > with `--iptables=false`. This is discussed upstream in the link above. > > In any case I will close this bug in the next changelog entry. >
Hey, this message was intended for bug #921600, sorry for the confusion! So, let's get back on the track: this very bug, #903635. As I mentioned above, there's a discussion with a work in progress to fix that upstream: https://github.com/docker/libnetwork/pull/2339 I don't think it will be ready in time for buster though. So I see two solutions going forward: - 1 Jonathan lower the severity of the bug so that it's not RC. - 2 I import the patch from github, even though it's work in progress. I will follow up and update the patch as soon as upstream release a proper fix, and it will be included in a point release of buster. If I don't get any feedback from you Jonathan in the following days, I'll go for solution number 2 then. Cheers
