Description of problem: If last container using given bridge stops, podman tears it down. Version-Release number of selected component (if applicable): RHEL 8.6 Podman How reproducible: Always Steps to Reproduce: 1. Containers are started during boot, using legacy network-scripts functionality. 2. Also run few services which we bind to the IP address of bridge. 3. When OS boots up, bridges are brought up, services started and bound to ipaddress. 4. Then we run containers which also use same bridge 5. It works just fine 6. But, If last container using given bridge stops, podman tears it down 7. This leaves OS without bridge that few services depend on. 8. Bridge itself is recreated by podman when new container using this bridge starts Actual results: Podman (netavark backend) tears down bridge on last container shutdown. Expected results: The bridge should not be affected by the fact that no containers are using it anymore.