mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-02 22:03:01 +02:00
Joachim Wiberg
674fd6c396
Previously at least one end of a veth pair had to remain in the host namespace, because that end created and destroyed the pair. Assigning both ends to containers left no one to create it. Select a deterministic primary end so exactly one side creates the pair. When the primary is itself a container interface, create the pair in the host namespace before the container starts; CNI host-device then moves each end into its container. Teardown is deferred to the container removal script so the pair does not linger and block re-creation. Drop the now-obsolete limitation notes from the documentation and YANG, and add a regression test connecting two containers over a veth pair. Fixes: #941 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
:testgroup: == Containers Tests verifying link:https://opencontainers.org/[OCI container] support: - Basic web server container running in host network mode - Container enable/disable functionality via configuration - Container environment variable configuration and access - Common setup with docker0 bridge and automatic VETH pairs - Connecting containers with VETH pairs to standard Linux bridges - Assigning physical Ethernet interfaces to containers - Container upgrades with persistent volume data - Container upgrade using RPC with cleanup of old image - Firewall container running in host network mode with full privileges include::basic/Readme.adoc[] <<< include::enabled/Readme.adoc[] <<< include::environment/Readme.adoc[] <<< include::bridge/Readme.adoc[] <<< include::phys/Readme.adoc[] <<< include::veth/Readme.adoc[] <<< include::volume/Readme.adoc[] <<< include::upgrade/Readme.adoc[] <<< include::firewall_basic/Readme.adoc[] <<< include::host_commands/Readme.adoc[]