Paul Holzinger
Paul Holzinger
yes because you have a default accept rule, change your firewall to default drop and it will no longer work. https://github.com/containers/netavark/issues/742
This is likely because we do not change any conntack entries in netavark. We must call into the kernel netlink API to drop the stale entries and last I check...
manually clear conntrack entries (assuming that is actually causing the issue you are having)
> Any way I can help troubleshoot why this is happening, and help fix it, so this work around isn't required? It happens because the kernel keeps the conntrack kernel...
This has never made it the top priority in our planning so at least in the near future we have no plans to work on this. That doesn't mean that...
Sorry for delay all, please apply through the official portal if you are interested, I think the applications should open later today. https://mentorship.lfx.linuxfoundation.org/project/07efb861-3c5b-4bc2-9986-593656750ffc As for easy issues it is hard...
Tests are failing
Also can you squash your commits please.
First this is already [documented](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...