podman/libpod/network/cni
Paul Holzinger 97c6403a1b
rename libpod nettypes fields
Some field names are confusing. Change them so that they make more sense
to the reader.
Since these fields are only in the main branch we can safely rename them
without worrying about backwards compatibility.
Note we have to change the field names in netavark too.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2021-11-16 19:19:04 +01:00
..
testfiles Network interface 2021-08-24 12:28:03 +02:00
README.md Network interface 2021-08-24 12:28:03 +02:00
cni_conversion.go podman machine improve port forwarding 2021-11-15 15:20:47 +01:00
cni_exec.go rootful: do not set XDG_RUNTIME_DIR for cni plugins 2021-09-24 11:25:02 +02:00
cni_suite_test.go Network interface 2021-08-24 12:28:03 +02:00
cni_types.go podman machine improve port forwarding 2021-11-15 15:20:47 +01:00
config.go netavark network interface 2021-11-11 15:54:02 +01:00
config_test.go podman machine improve port forwarding 2021-11-15 15:20:47 +01:00
network.go podman machine improve port forwarding 2021-11-15 15:20:47 +01:00
run.go rename libpod nettypes fields 2021-11-16 19:19:04 +01:00
run_test.go rename libpod nettypes fields 2021-11-16 19:19:04 +01:00

README.md

This package abstracts CNI from libpod. It implements the ContainerNetwork interface defined in libpod/network/types/network.go for the CNI backend.

Testing

Run the tests with:

go test -v -mod=vendor -cover ./libpod/network/cni/

Run the tests as root to also test setup/teardown. This will execute CNI and therefore the cni plugins have to be installed.