Why DNAT rules for a running container gets tampered when starting a container with similar port mapping configuration on Red Hat Enterprise Linux ?
Issue
- Why DNAT rules for a running container gets altered when starting a container with similar port mapping configuration on Red Hat Enterprise Linux ?
Environment
- Red Hat Enterprise Linux 8/9
- podman-4.9.4-X with netavark backend
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
