mirror of
https://github.com/kernelkit/infix.git
synced 2026-07-22 01:13:00 +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>
35 lines
687 B
YAML
35 lines
687 B
YAML
---
|
|
|
|
- name: Container Basic
|
|
case: basic/test.py
|
|
|
|
- name: Container Enabled/Disabled
|
|
case: enabled/test.py
|
|
|
|
- name: Container Environment Variables
|
|
case: environment/test.py
|
|
|
|
- name: Container with Bridge Network
|
|
case: bridge/test.py
|
|
|
|
- name: Container with Physical Interface
|
|
case: phys/test.py
|
|
|
|
- name: Container with VETH Pair
|
|
case: veth/test.py
|
|
|
|
- name: VETH Pair Between Two Containers
|
|
case: internal_link/test.py
|
|
|
|
- name: Container Volume Persistence
|
|
case: volume/test.py
|
|
|
|
- name: Container Upgrade
|
|
case: upgrade/test.py
|
|
|
|
- name: Basic Firewall Container
|
|
case: firewall_basic/test.py
|
|
|
|
- name: Host Command Execution from Container
|
|
case: host_commands/test.py
|