podman/libpod/network/netavark
Paul Holzinger 044edbb9c9
Fix netavark error handling and teardown issue
The return error was not returned by podman , instead a different error
was created. Also make sure to free assigned ips on an error to not leak
them.

Lastly podman container cleanup uses the default network backend instead
of the provided one, we need to add `--network-backend` to the exit
command.

[NO NEW TESTS NEEDED]

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2021-11-22 17:49:55 +01:00
..
testfiles netavark network interface 2021-11-11 15:54:02 +01:00
config.go netavark network interface 2021-11-11 15:54:02 +01:00
config_test.go netavark network interface 2021-11-11 15:54:02 +01:00
const.go netavark network interface 2021-11-11 15:54:02 +01:00
exec.go Make sure netavark output is logged to the syslog 2021-11-19 18:15:53 +01:00
ipam.go netavark IPAM assignment 2021-11-11 16:25:19 +01:00
ipam_test.go netavark IPAM assignment 2021-11-11 16:25:19 +01:00
netavark_suite_test.go Add more netavark tests 2021-11-11 16:49:28 +01:00
network.go Make sure netavark output is logged to the syslog 2021-11-19 18:15:53 +01:00
run.go Fix netavark error handling and teardown issue 2021-11-22 17:49:55 +01:00
run_test.go Force iptables driver for netavark tests 2021-11-19 18:23:26 +01:00