network resources are leaked when error happens during setup #18205
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
network
Networking related issue or feature
Issue Description
The network resources are leaked when there is a error during the initial container setup process.
This effects both netavark and cni.
Steps to reproduce the issue
Make sure to not have containers running and try this as rootless
podman network create test1
podman run -p 80:80 --network podman1 alpine ip a
Which correctly fails with:
ps aux
Describe the results you received
See that aardvark-dns is still running, or dnsmasq when using CNI.
Describe the results you expected
Podman should teardown the network correctly on errors.
podman info output
latest main branch
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
This seems to be the root cause why we leak so many aardvark-dns or dnsmasq processes in e2e tests in CI.
The text was updated successfully, but these errors were encountered: