dfw won't start with crazy-max/docker-fail2ban:latest in place

[cybermcm]

I'm using dfw and crazy-max/docker-fail2ban in combination. Since the latest update of fail2ban dfw won't start any longer.
fail2ban underlying image was bumped to Alpine 3.23, not sure if this causes the issue

reverting fail2ban image to an older version solves the issue

error:

dfw  | , module: dfw:505
dfw  | Mar 08 08:07:34.349 INFO Application started, started_at: 2026-03-08T08:07:34.348000517Z, version: 1.3.0, module: dfw:298
dfw  | Mar 08 08:07:34.409 INFO Starting processing, started_processing_at: 2026-03-08T08:07:34.409143552Z, module: dfw::nftables::process:23
dfw  | Mar 08 08:07:34.441 INFO Finished processing, finished_processing_at: 2026-03-08T08:07:34.441762307Z, module: dfw::nftables::process:121
dfw  | Mar 08 08:07:34.441 INFO Applying rules (using nft), module: dfw::nftables:60
dfw  | Mar 08 08:07:34.455 ERRO Encountered error, backtrace: , error: NFTables error:

with debug the last lines in log:

dfw  | Mar 08 08:29:38.095 DEBG Add forward rule, rule: tcp dport 10051 ip daddr 172.18.1.4 meta iifname ens3 oifname br-4683c4115033 meta mark set 0xdf accept, part: wider_world_to_container, module: dfw::nftables::process:952
dfw  | Mar 08 08:29:38.095 DEBG Add DNAT rule, rule: tcp dport 10051 meta iifname ens3 meta mark set 0xdf dnat 172.18.1.4:10051, part: wider_world_to_container, module: dfw::nftables::process:956
dfw  | Mar 08 08:29:38.095 DEBG Add mark rule, rule: tcp dport 10051 meta iifname ens3 meta mark set 0xdf, part: wider_world_to_container, module: dfw::nftables::process:960
dfw  | Mar 08 08:29:38.095 INFO Finished processing, finished_processing_at: 2026-03-08T08:29:38.095396921Z, module: dfw::nftables::process:121
dfw  | Mar 08 08:29:38.095 DEBG Writing rules to temporary file, file_path: /tmp/.tmpomsNZE, module: dfw::nftables:50
dfw  | Mar 08 08:29:38.095 INFO Applying rules (using nft), module: dfw::nftables:60
dfw  | Mar 08 08:29:38.114 ERRO Encountered error, backtrace: , error: NFTables error: