Closed podhorsky-ksj closed 3 days ago
You cannot remove a network while it used and as there is no process attached it would be impossible to set up dependencies so that the unit would be stopped automatically after all referring containers units are stopped. As such we decided to just leak the networks. I think volume work in the same way.
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#network-units-network
Please note that stopping the corresponding service will not remove the podman network. In addition, updating an existing network is not supported. In order to update the network parameters you will first need to manually remove the podman network and then restart the service.
Issue Description
I'm fighting with network between containers. I cannot use pod, because I need to use different userns for every container (to have data in host with same uid as in container), which is impossible in pod.
I have found an issue with network quadlet. I have quadlet file sonarqube.network
I started it with systemctl --user start sonarqube-network systemctl --user stop sonarqube-network is ignored, also daemon-reload. I had to remove the network with podman network rm.
Steps to reproduce the issue
Describe the results you received
network must be removed with podman network rm.
Describe the results you expected
all quadlet files should work the same way, but network does not.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting