Podman network rm seems to be broken in some situations #9632
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.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
It seems that podman network rm forces using -f flag in places in which this flag should not be used. Please consider the case below.
I have created a fix proposal in #9622.
Steps to reproduce the issue:
podman network create foo
podman run --name bar --network foo -d alpine sleep 100000
podman network disconnect foo bar
podman network rm foo
Error: "foo" has associated containers with it. Use -f to forcibly delete containers and pods: network is being used
Describe the results you received:
Error: "foo" has associated containers with it. Use -f to forcibly delete containers and pods: network is being used
Describe the results you expected:
Network is not used. It should be deleted without -f flag
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Reproducible on debian, fedora
The text was updated successfully, but these errors were encountered: