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 dock
Package: docker.io
Version: 18.09.1+dfsg1-5+b10
Followup-For: Bug #921600
Bugs like these are very very disappointing. Our users are going to be
left out scratching heads and pulling hairs.
I'm not sure who to vent out the frustration on. docker has its own
iptables setup, the legacy one. So, for
On Thu, 7 Feb 2019 23:42:32 + "brian m. carlson"
wrote:
>
> Moreover, this package probably needs to conflict with the new iptables
> package, since it cannot usefully work in conjunction with it.
>From what I see, the iptables package provides both iptables-legacy and
iptables-nft. The docke
On Thu, Feb 07, 2019 at 11:12:36AM +0700, Arnaud Rebillout wrote:
> Hi,
>
> did you report that issue upstream? I found a related thread at:
>
> https://github.com/moby/moby/issues/26824
>
> This thread mentions a workaround: deactivate the iptables integration
> via |--iptables=false| and t
Hi,
did you report that issue upstream? I found a related thread at:
https://github.com/moby/moby/issues/26824
This thread mentions a workaround: deactivate the iptables integration
via |--iptables=false| and then set the right rules for nftables by hand.
I'm not so really familiar with net
Package: docker.io
Version: 18.09.1+dfsg1-5
Severity: important
I run Docker on my laptop to allow me to test various environments,
such as Debian stable. I also use ufw to provide a firewall to restrict
access to most ports.
However, these two programs are incompatible. ufw uses the
nftables-bas
6 matches
Mail list logo
