Rob Murray

> I do want to mention that the default behavior of setting the default policy to drop, **despite being set by the user to accept before the docker start** is...

> Oops, I forgot I had the following override, which was overwritten: > `ExecStartPost=/usr/sbin/ip6tables -P FORWARD ACCEPT` > > What is the proper way to fix this issue with the...

> Maybe we should just ditch this package altogether? WDYT @robmry? I think it's still useful to track where to start the search for the next free port (to avoid...

Hi @Martzki - `defer` only runs when a function returns. So, each iteration of the loop leaks a `Client`.

Do you still see the problem if you call `c.Close()` after using it in `c.ContainerList()`? How about with current versions of the docker client/engine?

Ok, thank you - the versions of docker you're using are years old, and no longer maintained, I can't repro the issue with recent versions of docker, and the client...

Hi @rodrigogonegit - I haven't been able to repro this, with Debian 12.5, firewalld 1.3.3 and docker 27.1.2 (and 27.2.0). After creating the network, it's in the `docker` zone -...

Hi @Tony763 - did you confirm it's the same issue by disabling firewalld as per the original description? Are you also using Debian 12.5, firewalld 1.3.3? If so, same questions...

> Hi @robmry, I am on Ubuntu Server 24.04 and I do not use firewalld but nftables instead. Ok, this issue is "Docker bridge networks not automatically added to appropriate...

Ok, thank you ... do you have `"iptables": false` in your `/etc/docker/daemon.json`? (Or `--iptables=false` on the command line?)