How to tell netavark to use firewalld instead of iptables

[unknowndevQwQ]

In the readme.md page, I saw that netavark supports both firewalld and iptables, but when using it, I found that netavark prefers iptables to firewalld. I tried to find the answer in the netavark documentation, but this did not use

[Luap99]

you can overwrite it with the NETAVARK_FW env var

netavark/src/firewall/mod.rs

Line 40 in ce1e004

if let Ok(var) = env::var("NETAVARK_FW") {

Ideally we would add this as field in containers.conf, see containers/common#1338

[Luap99]

Why do you want to set it via command line? We only support the use with podman and podman could just set the env so there is no need to add more code here.

[unknowndevQwQ]

Why do you want to set it via command line? We only support the use with podman and podman could just set the env so there is no need to add more code here.

One of the reasons for adding the command line option is for possible other programs to work well with netavark in the future, and secondly, the debug information currently output by podman never outputs env when executing commands, which is potentially troublesome for troubleshooting problems.

[unknowndevQwQ]

@Luap99 I want to do this thing, is it okay?

[Luap99]

Yes

[unknowndevQwQ]

Why is the noun driver instead of backend when netavark calls firewalld/ipt/nft?