Fail2ban docker not banning even if it says "already banned" about docker-fail2ban HOT 3 CLOSED

I have seen that the ban rules are inserted in iptables-legacy and not in iptables.
I can't use iptables-legacy as default since some other containers needs iptables nft.

does this image works with iptables-nft?

if yes, can I use both the REJECT rules from iptables nft and iptables legacy at the same time?
if yes, why
this line
REJECT all -- mob-myIP.net.vodafone.it anywhere reject-with icmp-port-unreachable
does not block my connection?

from docker-fail2ban.

I switched to iptables-legacy just to make a try...
update-alternatives --config ip6tables
update-alternatives --config iptables

rebooted the system.

iptables -L
shows that the ip is correctly banned but I have no problem in accessing my site...

Chain f2b-HASS (1 references)
target     prot opt source               destination         
REJECT     all  --  176.myip.0.0      anywhere             reject-with icmp-port-unreachable
RETURN     all  --  anywhere             anywhere      

from docker-fail2ban.

I solved by adding the DOCKER chain in the correct jail.

from docker-fail2ban.