netavark The default zone of firewalld used by podman is not trusted

Feature request description

For quite some time, the firewalld zone used by podman was trusted, but this behavior ran into some frustration when I tried to use trusted for its original purpose.

Suggest potential solution

When dealing with firewalld, start by creating a separate zone, such as "podman".

Have you considered any alternatives?

idk

Additional context

docker does not use trusted, but creates a docker zone for itself.

Mar 08 '23 01:03 unknowndevQwQ

@mheon PTAL

Mar 09 '23 17:03 Luap99

The firewalld driver will do this, when I finally get the time to finish it. Honestly, at this point, I should just find a weekend and hack it out, it's ~95% of the way there in functionality. Biggest obstacle is getting all the tests enabled for it.

Mar 09 '23 17:03 mheon

A friendly reminder that this issue had no activity for 30 days.

Apr 09 '23 00:04 github-actions[bot]

The firewalld driver will do this, when I finally get the time to finish it. Honestly, at this point, I should just find a weekend and hack it out, it's ~95% of the way there in functionality. Biggest obstacle is getting all the tests enabled for it.

What problems have you encountered in the unresolved 5 %?

Apr 09 '23 03:04 unknowndevQwQ