Legacy support for Docker containers running on Synology/QNAP

What is the name of the domain?

.

What is the error message?

2024-11-07T18:49:05.148Z WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: “”, stderr: “” } 2024-11-07T18:49:05.148Z WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256)) 2024-11-07T18:49:05.159Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1 2024-11-07T18:49:05.159Z WARN firewall::engine: fw.apply_config_changes failed e=ApplyError(“nft command failed with return code: 256”)

What is the issue you’re encountering

Both, Synology and QNAP uses old iptables as solution to implement firewall needs. warp-sec seems to use nft command.

What steps have you taken to resolve the issue?

On container image based on debian bookworm, ?'ve tried to switch to iptables and use update-alternatives so iptables-legacy is used as default firewall framework, with no luck.

What are the steps to reproduce the issue?

Run warp-svc connector on a linux system with iptables as default firewall solution and no notables packages installed.