containers
/
automation-tests
mirror of https://github.com/containers/automation-tests.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
automation-tests/common/libnetwork/cni
History
Paul Holzinger 70d14082ea pkg/netns: UnmountNS() accept netns path as string 
I want to switch podman over to only using strings for the netns path.
So we no longer pass this interface around. Buildah doesn't use this so
we only need to fix it in Podman. I have a WIP PR[1] for that.

[1] https://github.com/containers/podman/pull/16756

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
 		2022-12-07 14:53:47 +01:00
..
testfiles libnetwork/cni: add isolate option 2022-07-07 16:26:11 +02:00
README.md add libnetwork package 2021-12-16 19:07:38 +01:00
cni_conversion.go bump to golangci-lint v1.50.0 2022-10-17 15:03:07 +02:00
cni_exec.go Build libnetwork/cni on FreeBSD 2022-05-14 10:55:32 +01:00
cni_suite_test.go Switch to ginkgo/v2 2022-03-30 10:03:17 +02:00
cni_types.go libnetwork/cni: fix panic with ipam driver none 2022-12-05 17:55:03 +01:00
config.go libnetwork: extend API to support NetworkUpdate 2022-12-07 07:53:02 +05:30
config_freebsd.go Build libnetwork/cni on FreeBSD 2022-05-14 10:55:32 +01:00
config_linux.go Build libnetwork/cni on FreeBSD 2022-05-14 10:55:32 +01:00
config_test.go libnetwork: extend API to support NetworkUpdate 2022-12-07 07:53:02 +05:30
network.go Vendor in latest containers/(storage, image) 2022-12-05 10:04:10 -05:00
run.go Switch to golang native error wrapping 2022-07-12 10:54:07 +02:00
run_freebsd.go Build libnetwork/cni on FreeBSD 2022-05-14 10:55:32 +01:00
run_linux.go Build libnetwork/cni on FreeBSD 2022-05-14 10:55:32 +01:00
run_test.go pkg/netns: UnmountNS() accept netns path as string 2022-12-07 14:53:47 +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.